Search Results get_os_rules

Overview

FND_DEBUG is a core Oracle E-Business Suite infrastructure package owned by the APPS schema. Its business function is to provide a centralized runtime debugging and rule-evaluation framework used across the EBS technology stack. Rather than each product team embedding ad hoc logging, FND_DEBUG exposes a governed API through which conditional debug rules can be enabled, disabled, queried, and executed. This allows developers, DBAs, and support analysts to activate fine-grained diagnostics on a live instance without modifying application code, restarting services, or redeploying forms.

The package is a dependency of FND_CONCURRENT, the concurrent manager processing package, confirming its role in the foundation layer of the application. Multiple products and frameworks reference FND_DEBUG to gate their own diagnostic output. The API is classified as OTHER rather than a business-facing API, reflecting its technical and administrative purpose.

Key Procedures and Functions

• ENABLE_DB_RULES — Activates database-side debug rules that have been configured in the debug rule repository, making them eligible for evaluation during runtime execution.
• DISABLE_DB_RULES — The inverse operation, deactivating database debug rules so that they are no longer evaluated, typically used to reduce overhead after a diagnostic session.
• GET_OS_RULES — Retrieves operating-system-level debug rules, allowing the framework to account for external or process-level conditions when determining whether diagnostics should fire.
• GET_RET_VALUE — Returns the outcome value associated with a rule evaluation, enabling calling code to branch based on whether a debug condition was satisfied.
• GET_TRANSACTION_ID — Obtains the current transaction identifier, which is used to correlate debug rule executions with the specific business transaction under investigation.
• ASSIGN_REQUEST — Associates a concurrent request with the debug framework, so that diagnostics enabled for a session can be tied to a specific request ID for traceability.

No parameter signatures are documented in the ETRM metadata; consumers should reference the package specification in the database for exact argument lists.

Tables Accessed

• FND_DEBUG_OPTIONS — Stores the defined debug options available within the framework.
• FND_DEBUG_OPTION_VALUES — Holds the values assigned to those options for a given debug configuration.
• FND_DEBUG_RULES — The master repository of debug rules, defining when diagnostics should be activated.
• FND_DEBUG_RULE_OPTIONS — Maps rules to the debug options they control.
• FND_DEBUG_RULE_EXECUTIONS — Records each instance a rule was evaluated or fired, supporting audit and troubleshooting.
• DUAL — Used for scalar expression evaluation and lightweight PL/SQL constructs.

Usage Notes

FND_DEBUG is normally invoked indirectly. The concurrent manager (FND_CONCURRENT) and product frameworks call it to evaluate whether debug logging should be switched on for a running request. Administrators configure rules and options through the Debug Options setup, and the corresponding profile options govern which rules apply. Custom code may call the package directly to honour the same rule definitions and to register a request via ASSIGN_REQUEST. Because rule evaluation carries a performance cost, rules are typically disabled outside active diagnostic windows. All references resolve through APPS synonyms, so fully qualified invocation as APPS.FND_DEBUG is standard practice.