Search Results report_errors




Overview

FEM_GENDEFAULTS_ENG_PKG is a private implementation package belonging to the Oracle Enterprise Taxation and Revenue Management (ETRM) schema family, deployed under the APPS account in Oracle E-Business Suite 12.1.1 and 12.2.2. The package body carries the enumeration source file name fem_gendflt_eng.plb (revision 120.0, checked in by Rob Flippo on 11 July 2006), which indicates that it is the body portion of a specification/body pair whose public interface is declared in fem_gendefaults_eng.pls. As the package specification directs the reader to the specification for a full description, the body's stated purpose is to provide the runtime logic that supports generic default value generation within the ETRM application.

The package is classified in the ETRM metadata as API classification OTHER, meaning it is not a standard public open interface (such as an Applications Program Interface intended for external callers). It is instead an internal engine package whose procedures are expected to be called by other ETRM packages, concurrent programs, or forms-layer code that require defaulting logic to be resolved programmatically. The specification exposes a single documented program unit, MAIN.

Key Procedures and Functions

  • MAIN — The single documented program unit in the package. As the named public entry point, MAIN serves as the driver or dispatcher for the defaulting engine, orchestrating whatever internal logic the body contains to populate or resolve application defaults. Its parameter list is not recorded in the ETRM metadata excerpt and is not reproduced here.
  • REPORT_ERRORS (private) — Although not listed among the documented public procedures, the package body source explicitly declares and defines a private procedure Report_Errors. Its description states that it "retrieves messages from the stack and reports them to the appropriate log." It is scoped PRIVATE and was created by Rob Flippo on 02 May 2005. It operates without documented arguments and uses DBMS_UTILITY to capture the call stack, combining that with a package-level message buffer (gv_prg_msg, gv_callstack) to emit diagnostics through Oracle Application Object Library's FND_LOG facility. This is the object associated with the search term "report_errors."

Tables Accessed

The ETRM documented metadata records DBMS_UTILITY as the only referenced dependency, accessed through an APPS synonym. DBMS_UTILITY is an Oracle-supplied PL/SQL package rather than an application table; the engine uses it to obtain the current call stack (for example, DBMS_UTILITY.FORMAT_CALL_STACK) so that error context can be written to the FND log. No ETRM application tables or views are documented as being read or written by this package in the supplied metadata. The absence of table references is consistent with the package's role as a defaulting engine whose data access, if any, is delegated to subordinate packages or to the MAIN routine's runtime arguments rather than being statically bound at parse time.

Usage Notes

FEM_GENDEFAULTS_ENG_PKG is not invoked directly by end users. It is typically called from within ETRM application logic — custom code, concurrent program wrappers, or forms-based processes — that need defaults resolved under program control. Because the package is classified as OTHER rather than as a public API, Oracle support does not guarantee signature stability across patches; customizations should reference the specification rather than the body. The package declares six log-level constants mapped to FND_LOG levels (statement through unexpected) and a package-level v_log_level variable, indicating that diagnostics are gated by the standard FND Debug logging framework. When troubleshooting, DBMS_OUTPUT alone will not reveal messages from REPORT_ERRORS; FND_LOG must be enabled for the relevant module and level. The "report_errors" search term corresponds to this private diagnostics routine rather than to a documented public procedure, so it will not appear in the ETRM public API inventory.