Results for “get_transaction_id”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FND_DEBUG is the Oracle E-Business Suite foundation package that implements the FND Debugging framework, the mechanism by which administrators and developers enable, trace, and diagnose application behavior at runtime without modifying code. The package body maintains an in-memory collection of active debug rules (typed as rules_tab_type, indexed by binary_integer) and matches those rules against the current runtime context — user, responsibility, application, component type, component name, and component identifier — to determine which debug options should be enabled for the caller.

Its central design objective is context-sensitive diagnostics: rather than globally switching on trace or logging behavior, FND_DEBUG evaluates rules persisted in the FND_DEBUG_RULES hierarchy and returns the appropriate debug string for the component instance. The package body's comment header for the private helper enable_db_rules describes this contract precisely: it executes matching rules for the active user/responsibility, returns a string containing the debug string for the component instance, and returns TRUE if at least one rule executed on the call, otherwise FALSE. Rule evaluation honors validity windows (start_time, end_time), repeat counters (repeation_counter), and optional enable/disable exit routines, which is why the internal record structures carry both enable_routine and disable_routine fields.

Key Procedures and Functions

  • ENABLE_DB_RULES — Evaluates the debug rules currently applicable to the calling session's user, responsibility, and component context and enables the matching database-level debug behavior. This is the primary entry point invoked when an instrumented program requests debugging.
  • DISABLE_DB_RULES — Performs the inverse operation, deactivating database-level debug rules for the current context so that tracing or logging ceases.
  • GET_OS_RULES — Retrieves rules of the operating-system (server-side trace/log file) variety, complementing the database rule path. The underlying structures reference trace_file_routine and trace_file_node, which support trace file placement on a given application tier node.
  • GET_RET_VALUE — Returns the debug string or return value accumulated from rule execution, allowing the caller to consume the effective debug settings as a single value.
  • GET_TRANSACTION_ID — Supplies the transaction identifier associated with the current debugging context, used to correlate debug rule executions with a specific runtime transaction.
  • ASSIGN_REQUEST — Associates the debugging session with a concurrent request, binding rule activity to the request identifier (request_id) recorded on FND_DEBUG_RULES so diagnostics can be traced to a specific concurrent program run.

Tables Accessed

  • FND_DEBUG_OPTIONS — Master list of available debug options.
  • FND_DEBUG_OPTION_VALUES — Values for each option, including enable/disable routine names and trace file routine and node settings.
  • FND_DEBUG_RULES — Persisted rule definitions with validity windows, repeat counters, user/responsibility scope, component scope, comments, and request ID.
  • FND_DEBUG_RULE_OPTIONS — Junction of rules to the option name/value pairs a rule activates.
  • FND_DEBUG_RULE_EXECUTIONS — Execution history used to track rule invocations and repeat counting.
  • DUAL — Used for scalar evaluations and PL/SQL-side queries.

Usage Notes

FND_DEBUG is classified as OTHER and is referenced by one other package, but in practice it is invoked by instrumented application code and by the FND debug administration forms. Typical invocations occur when a developer or support analyst enables debugging from the Help > Diagnostics menu or the Debug Options form, after which framework code calls ENABLE_DB_RULES at session/component entry and DISABLE_DB_RULES at exit or session end. Concurrent programs that honor debug rules use ASSIGN_REQUEST to tie diagnostics to the request ID. Custom code may call GET_RET_VALUE to obtain the resolved debug string, and GET_OS_RULES when trace-file-level diagnostics are required. Because the package caches active rules in a package-level collection, changes to FND_DEBUG_RULES take effect only on re-evaluation or session restart.