Search Results p_exception_level

Overview

The package body APPS.VEA_EXCEPTIONS_SV is a table handler (also referred to as a "SV" or server-side validation/storage package) within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environment. It belongs to the VEA module, which corresponds to the Oracle EDI Gateway / e-Commerce Gateway product family used for electronic data interchange processing. The package encapsulates the core data manipulation logic for the VEA_EXCEPTIONS table, providing a consolidated, reusable interface through which application code — principally Oracle Forms — can create, modify, and query exception records generated during EDI transaction processing.

The documented header comment identifies the package purpose as a "Table handler package for table VEA_EXCEPTIONS." The existence of this abstraction layer reflects a standard Oracle EBS development pattern in which direct DML against a base table is centralized in a single package so that audit columns, validation rules, and error-handling conventions are applied consistently across every calling program.

Key Procedures and Functions

The excerpt provided documents the insert_row procedure. insert_row inserts a new record into the VEA_EXCEPTIONS table. Consistent with the table-handler pattern, it accepts the business columns of the table as input parameters — including the exception identifier, release identifier, layer provider code, message name, exception level, message text, and description — and populates the mandatory audit columns on behalf of the caller. The audit columns (created_by, creation_date, last_updated_by, last_update_date, and last_update_login) are derived from the internal utility package vea_tpa_util_pvt, which supplies the current user and login identifiers.

The procedure also declares a local location variable and an l_api_name constant, indicating that it follows the standard Oracle EBS API error-handling convention, in which a location string is progressively set so that exceptions can be reported with sufficient diagnostic context.

The ETRM metadata records no additional documented procedures or functions for this package body. The source header further notes the script that must be run to compile it (VEAVAPKB.pls) and traces its origin to 2000, with the last recorded revision dated 2003.

Tables Accessed

• VEA_EXCEPTIONS — the primary base table managed by this package. The insert_row procedure performs a direct INSERT into this table, populating the business columns supplied by the caller together with the system-maintained audit columns.
• VEA_EXCEPTIONS_S — an APPS synonym associated with the same exception entity, referenced by the package for validation or lookup purposes consistent with the table-handler design.
• DUAL — used for evaluation of system values, principally the retrieval of the current date and user context through SYSDATE and the utility functions.

Usage Notes

Packages of the _SV type in Oracle EBS are typically invoked from Oracle Forms-based user interfaces and, less frequently, from concurrent programs or custom PL/SQL extensions. In this case, the record is most likely surfaced to users through a maintenance form associated with the e-Commerce Gateway exception inquiry functionality, where operators review exceptions flagged during inbound or outbound EDI processing.

The user search term p_exception_level corresponds directly to the exception_level column of VEA_EXCEPTIONS and is the fourth business parameter of insert_row. That column classifies the severity or category of a given exception, enabling downstream reporting and filtering. Because the audit columns are set internally, callers are not required to supply them, and direct DML against VEA_EXCEPTIONS outside this package is discouraged. The package is referenced by no other documented packages in the ETRM metadata, indicating that its primary consumers are external UI or process components rather than peer PL/SQL packages.