Search Results output_line

Overview

HR_SECURITY_UTILS is an internal utility package in the APPS schema that supports Oracle E-Business Suite security profile processing, primarily within the Human Resources (PER) module. In releases 12.1.1 and 12.2.2 the package serves as a shared library that other HR security components call to validate profile option configuration, derive business group and security profile relationships, and route diagnostic messages. It is not a public API in the traditional sense; the ETRM classification for the package body is OTHER, reflecting its role as an infrastructure helper rather than a business-facing interface.

A significant portion of the package body is devoted to private support routines. The source excerpt shows helpers such as RAISE_ERROR, which raises a generic application error, and DEBUG_ON / DEBUG_OFF, which toggle an internal BOOLEAN flag (debug_mode_on). The OUTPUT_LINE procedure checks that flag and, when debugging is active or the caller forces output, emits a message. Notably, the implementation directs messages to HR_UTILITY.TRACE rather than DBMS_OUTPUT.PUT_LINE, a change introduced under Bug#885806. Callers searching for "output_line" are typically looking at this trace facility while troubleshooting security profile behavior.

Key Procedures and Functions

The ETRM metadata documents five named program units on this package:

• CHECK_PROFILE_OPTIONS — The principal public procedure. It reads security-related profile option values at Site, Application, and Responsibility levels, then reconciles them against PER_BUSINESS_GROUPS and PER_SECURITY_PROFILES. It is the entry point most external callers use.
• DEBUG_ON — Private helper that enables the internal debug flag, causing OUTPUT_LINE to emit trace text.
• DEBUG_OFF — Private helper that disables the debug flag and suppresses routine trace output.
• IS_CUSTOM_SCHEMA — Returns the state of the custom_schema package variable, indicating whether the session is running against a custom schema.
• SET_CUSTOM_SCHEMA — Assigns the custom_schema flag, allowing callers to declare the schema context.

Additional private units visible in the source, including RAISE_ERROR, OUTPUT_LINE, and the nested GET_DETAILS routine, are not separately documented in ETRM but form the internal plumbing used by these five programs.

Tables Accessed

Through APPS synonyms, the package references the following objects:

• FND_PROFILE_OPTIONS — Supplies profile option definitions used to determine which security profile options apply to the current context.
• FND_PROFILE_OPTION_VALUES — Provides the actual Site, Application, and Responsibility level values set for those profile options.
• PER_SECURITY_PROFILES — Delivered security profiles used to map defined profiles back to their owning business group.
• DBMS_OUTPUT — Appears in the table list because the earlier OUTPUT_LINE implementation used PUT_LINE; the current code routes output through HR_UTILITY.TRACE instead, though DBMS_OUTPUT remains part of the package's technical footprint.

Usage Notes

HR_SECURITY_UTILS is invoked indirectly rather than by end users. It is referenced by one other documented package and is most commonly exercised when HR security profile options are validated during forms navigation, responsibility startup, or security administration activities. Developers diagnosing security profile mismatches can enable tracing through DEBUG_ON so that OUTPUT_LINE writes diagnostic messages to the HR_UTILITY trace destination; the trace text is then reviewed through standard EBS trace file inspection. Custom code should treat the documented procedures as internal utilities and avoid hard dependency on the private debug and output routines, since their signatures are not part of a committed public API and may change between 12.1.1 and 12.2.2.