Search Results update_error

Overview

DPP_ERROR_PVT is a private PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified as a PVT (private) API within the ETRM (Enterprise Transaction and Reporting Management) module. Its role is to capture and persist error information generated during the processing of transaction headers and their associated transaction lines. The package provides a structured mechanism for recording execution-level failures, including the offending transaction header, operating unit, execution detail reference, and an XML payload that carries the detailed error content. This design supports downstream diagnostics, reprocessing decisions, and auditability of transaction failures.

The package declaration is defined with AUTHID CURRENT_USER, meaning that runtime privileges are evaluated against the invoking schema rather than the defining schema. The embedded header comment ($Header: dppverrs.pls 120.1 2007/12/13) indicates the package has been stable since the 12.1.x code generation and remains present in the 12.2.2 release.

Two central constructs are declared in the specification. The first is DPP_ERROR_REC_TYPE, a record type that models a single error event with attributes such as Transaction_Header_ID, Org_ID, Execution_Detail_ID, the Output_XML CLOB containing error details, Provider_Process_Id, Provider_Process_Instance_id, and Last_Updated_By. The second is dpp_lines_tbl_type, a PL/SQL associative array indexed by BINARY_INTEGER whose element type mirrors DPP_TRANSACTION_LINES_ALL.TRANSACTION_LINE_ID%TYPE. This table type enables callers to pass a set of transaction line identifiers to be associated with the error record without relying on a database collection type.

Key Procedures and Functions

The ETRM metadata documents one public subprogram in the package: UPDATE_ERROR. According to the specification, it takes the standard Oracle API parameter block — p_api_version, p_init_msg_list, p_commit, p_validation_level — together with output parameters x_return_status, x_msg_count, and x_msg_data. Two business parameters complete the signature: p_exe_update_rec of type DPP_ERROR_REC_TYPE and p_lines_tbl of type DPP_LINES_TBL_TYPE.

The procedure's stated purpose is simply "Update Error." Its contract is to accept a populated error record and an optional collection of transaction line identifiers and to persist or update the error state accordingly. The presence of the standard FND_API message-count and return-status outputs indicates the procedure adheres to Oracle's API error-handling conventions, allowing callers to inspect success or failure and retrieve stacked messages when a call does not succeed.

Tables Accessed

The documented tables referenced by the package (through APPS synonyms) are DPP_TRANSACTION_LINES_ALL and PLITBLM. DPP_TRANSACTION_LINES_ALL is the transaction-lines base table for the module; the package reads its TRANSACTION_LINE_ID column type definition to build dpp_lines_tbl_type, and uses the identifiers passed in p_lines_tbl to relate error records to the specific lines that failed. PLITBLM is a standard Oracle EBS message-handling table used for localized or stacked error text; its inclusion here confirms that the package maintains structured error messaging consistent with the FND message framework.

The DPP_ERROR_REC_TYPE record also implies access to an execution-detail store keyed by Execution_Detail_ID, and to header-level information keyed by Transaction_Header_ID and Org_ID, allowing the update to be scoped correctly within the multi-org context.

Usage Notes

DPP_ERROR_PVT is a private package and is not intended for direct invocation by external applications. It is referenced by one other package within the ETRM codebase, which acts as the public-facing entry point and delegates error-update operations to UPDATE_ERROR. Because of the AUTHID CURRENT_USER clause and the private classification, custom code should not call this package directly; customizations should use the documented public API that wraps it.

Typical invocation occurs during batch or concurrent processing of DPP transactions, when a line or header fails validation or processing and the error must be logged with its diagnostic XML and associated transaction line identifiers. Callers populate the error record and line table, then call UPDATE_ERROR with the standard validation level and commit flag, checking x_return_status and the message outputs to confirm the update. This pattern keeps error recording consistent, multi-org aware, and compatible across EBS 12.1.1 and 12.2.2.