Search Results next_record

Overview

FND_OAM_KBF_SUBS is a PL/SQL package body owned by APPS within the Oracle E-Business Suite Applications Technology layer. Its header signature ($Header: AFOAMSBB.pls 120.1.12010000.2 2008/08/12) confirms its origins in the Oracle Applications Manager (OAM) diagnostic infrastructure, specifically the Knowledge Base Framework (KBF) supporting the Business Exception ("BIZEX") notification subsystem. Functionally, the package governs subscription logic for business exception notifications: it determines which registered subscriptions should receive a notification for a given exception, evaluates whether a notification has already been dispatched to avoid duplicates, and constructs the resulting notification documents. It does not expose a public API in the conventional sense; the ETRM classification is OTHER, reflecting that this is an internal engine consumed by the OAM notification framework rather than a documented integration point. The package carries private helper logic (for example HAS_NOTIFIED, which queries the sent-notification table by subscription and unique exception identifier, and SHALL_ADD_SUBS, which applies matching rules such as blank or 'ANY' item scoping) in addition to the documented entry points.

Key Procedures and Functions

Four procedures and functions are documented for this package:

• CREATESUBLIST — Builds the list of subscriptions applicable to a given business exception event. It represents the core routing decision: assembling the candidate subscribers that pass the matching and de-duplication checks before notification is attempted.
• CREATESUBJECT — Generates the subject line text for the outbound exception notification, derived from the exception context and subscription metadata.
• CREATEBUSEXCEPDOC — Constructs the business exception notification document itself, the payload delivered to the subscriber.
• CREATEBUSEXCEPDOCPART1 — Creates the first (or primary) part of that notification document, indicating the document is assembled in multiple fragments, likely to accommodate message size or mixed content types.

No parameter lists are asserted here beyond those evidenced in the source excerpt for the private helpers; the documented procedures are described by purpose only.

Tables Accessed

The package reads and writes OAM business exception and logging tables through APPS synonyms, most notably FND_OAM_BIZEX_SUBSCRIP (subscription definitions), FND_OAM_BIZEX_SENT_NOTIF (dispatch history, used by HAS_NOTIFIED to prevent duplicate sends), and FND_LOG_EXCEPTIONS / FND_LOG_UNIQUE_EXCEPTIONS (the exception registry supplying UNIQUE_EXCEPTION_ID). Supporting reads touch FND_LOG_MESSAGES and FND_LOG_TRANSACTION_CONTEXT for message and session context. The package also resolves metadata for referenced concurrent programs, forms, functions, and queues via FND_APPLICATION, FND_CONCURRENT_PROGRAMS and its _TL table, FND_CONCURRENT_QUEUES and _TL, FND_FORM, FND_FORM_TL, FND_FORM_FUNCTIONS, and FND_FORM_FUNCTIONS_TL — used to translate exception context into human-readable notification content.

Usage Notes

FND_OAM_KBF_SUBS is invoked internally by the OAM business exception notification framework, typically triggered when the logging subsystem detects an exception that has subscriptions registered against it. It is not referenced by any other documented package (0 dependents), which confirms its role as a leaf-level implementation unit behind the OAM Diagnostics / Business Exception UI. Because the "next_record" search term surfaces this object, developers should note that cursor-advance behavior is supplied by the surrounding OAM iteration logic; this package provides the content and eligibility decisions rather than a public
record-navigation API. Custom code should not call these procedures directly; the supported entry point for exception subscription remains the Oracle Applications Manager interface.