Results for “open_file”

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

Overview

FND_CORE_LOG is a server-side PL/SQL package body owned by the APPS schema that provides the centralized logging facility for the Oracle E-Business Suite Release 12.1.1 and 12.2.2 applications tier. Its principal business function is to allow application code — Oracle-provided or customer-written — to write controlled diagnostic output to a file on the database server without embedding ad hoc file-handling logic in each program. The package encapsulates profile-driven enablement, file lifecycle management, and the actual text-writing operations, so that a developer needs only a single call to emit a debug or trace message.

The package is classified as OTHER rather than as a public business API, reflecting its role as internal infrastructure rather than a supported integration interface. It is not referenced by any database object in the dependency chain, meaning no other stored object compiles against it, while it itself depends on a small, well-defined set of dictionary views, profile tables, and built-in packages.

Key Procedures and Functions

The ETRM metadata documents thirteen procedures and functions within the package body. Their purposes are as follows.

• ENABLED and IS_ENABLED — determine whether logging is currently switched on, gating all subsequent write activity so that disabled logging incurs negligible overhead.
• PROFILE_TO_LOG — resolves the configured logging target or destination from profile option settings.
• WRITE, WRITE_PROFILE, and WRITE_PROFILE_SAVE — high-level write entry points. WRITE emits a message directly; WRITE_PROFILE emits a message associated with a resolvable profile context; WRITE_PROFILE_SAVE preserves the logging configuration or pending output.
• PUT, PUT_LINE, and NEW_LINE — low-level output primitives mirroring the familiar UTL_FILE semantics: PUT appends text without a terminator, PUT_LINE appends text followed by a line terminator, and NEW_LINE emits a blank line for readability.
• PUT_NAMES — writes identifying context information, such as the calling program or session identifiers, to the log.
• OPEN_FILE and CLOSE_FILE — manage the underlying file handle, opening the destination log file for writing and releasing it when the logging block completes.

No parameter signatures are documented in the available metadata, and none should be assumed; callers should consult the package specification in the target release.

Tables Accessed

FND_CORE_LOG reads the profile option infrastructure through the APPS synonyms FND_PROFILE_OPTIONS and FND_PROFILE_OPTION_VALUES. These supply the site-level and user-level settings that determine whether logging is active and where output is directed, which is why enablement is resolved at runtime rather than hard-coded.

Supporting dependencies include DBMS_UTILITY for session and call-stack identification, DUAL for trivial queries, UTL_FILE for server-side file input and output, and the dynamic performance views V$INSTANCE and V$PARAMETER, used to identify the instance and to inspect initialization parameters such as the UTL_FILE_DIR or directory object configuration that governs file placement.

Usage Notes

FND_CORE_LOG is typically invoked from custom PL/SQL that follows the standard EBS pattern: the calling program checks IS_ENABLED or ENABLED, calls OPEN_FILE, issues one or more WRITE, PUT_LINE, or PUT_NAMES calls, and finally calls CLOSE_FILE. It is also referenced by two other packages, indicating reuse by Oracle-delivered components.

Because output is written through UTL_FILE to a server-side directory, the database administrator must ensure the target directory is properly registered and that the APPLSYSPUB/APPS operating-system account holds write privileges. The relevant FND profile options must be set appropriately before logging produces any output. Developers are cautioned that FND_CORE_LOG is diagnostic instrumentation, not an auditing mechanism: its output is not transactionally protected, is not visible to end users in the application forms, and should not be used to satisfy compliance or reconciliation requirements. In Release 12.2.2, on-premise deployments should also be aware that the package is not a supported extension point, so custom code should treat its behavior as version-dependent.