Search Results lock_update_row

Overview

CN_IMP_HEADERS_PKG is a PL/SQL package in the APPS schema that encapsulates the core data manipulation logic for the CN_IMP_HEADERS table, which stores import header records used by the Oracle E-Business Suite Channel Management / Trade Management (CN) import and validation process. The package is declared with AUTHID CURRENT_USER, meaning that name resolution and privilege checking for referenced database objects are performed against the invoker's schema rather than the definer's schema; this allows the package to operate correctly when invoked from contexts where the APPS synonym set is available and shifts privilege checking to the calling session. The package supplies a standard CRUD-style interface built around a single record type, CN_IMP_HEADERS_PVT.IMP_HEADERS_REC_TYPE, so that callers pass a single structured record representing an import header row rather than long positional parameter lists. It is classified as OTHER in the ETRM inventory and is the primary write path for import header staging data used by import validation and processing programs.

Key Procedures and Functions

• INSERT_ROW — The main insert procedure. It accepts one import header record. Per the source notes, the primary key must be populated by the caller from the relevant sequence before this procedure is called; the procedure itself contains no sequence reference. All parameters are IN parameters.
• UPDATE_ROW — The main update procedure. It accepts one import header record and overwrites the target row. The documentation explicitly notes that no object version checking is performed and that overwriting may occur. Callers that require object version checking are directed to use LOCK_UPDATE_ROW instead. All parameters are IN parameters, and the procedure may raise NO_DATA_FOUND if no record is updated.
• LOCK_UPDATE_ROW — The main lock-and-update procedure. It performs object version checking before applying the update, guarding against lost updates when concurrent sessions modify the same import header. It accepts one import header record and, like UPDATE_ROW, may raise NO_DATA_FOUND if no record is updated. This is the procedure most closely associated with the "lock_update_row" search term and is the recommended entry point where optimistic concurrency control is required.
• DELETE_ROW — The delete procedure for import header records, completing the package's row-level lifecycle interface.

Tables Accessed

The package operates against CN_IMP_HEADERS, the base table holding import header rows, and is documented as referencing DUAL, typically for lightweight checks or default value evaluation during procedure execution. All access is performed through APPS synonyms. INSERT_ROW, UPDATE_ROW, LOCK_UPDATE_ROW, and DELETE_ROW write to CN_IMP_HEADERS; the table is the sole persistent object maintained by the package, and DUAL is used only as a read-only utility reference.

Usage Notes

CN_IMP_HEADERS_PKG is invoked from other PL/SQL units in the Channel Management import flow rather than from a form directly; ETRM records that it is referenced by one other package. Typical invocation patterns are import validation and processing concurrent programs, custom import loaders, and API-layer packages that construct an IMP_HEADERS_REC_TYPE record and then call INSERT_ROW, UPDATE_ROW, LOCK_UPDATE_ROW, or DELETE_ROW. Because the package is AUTHID CURRENT_USER, callers must have the necessary object privileges; when invoked through APPS-connected sessions or concurrent programs, the APPS synonyms resolve normally. When updating headers that may be concurrently maintained, LOCK_UPDATE_ROW should be preferred over UPDATE_ROW, since UPDATE_ROW performs no object version comparison and can silently overwrite intervening changes. The header in the source file (cntimhrs.pls, 115.2) indicates the package has remained stable since early releases and is functionally consistent across EBS 12.1.1 and 12.2.2.