Search Results t_def_jeopardy_tmr

Overview

XNP_T_DEF_JEOPARDY_TMR_U is a message-generation package body owned by APPS within the Oracle E-Business Suite Order Management and Advanced Supply Chain Planning messaging infrastructure. It belongs to the XNP family of PL/SQL objects that construct and dispatch XML-based business messages between EBS modules, trading partners, and external systems. This particular package targets the T_DEF_JEOPARDY_TMR message type, which conveys Time Measurement Request data associated with jeopardy conditions — that is, supplier or order-line situations where a commitment date may be at risk. The "_U" suffix in the module name conventionally indicates a user-facing generation stub, while the header tag XNPJPTMB.pls and version stamp 120.2 (2006/02/13) confirm its origin as a shipped EBS source file. The package's core responsibility is assembling the XML payload, header metadata, and delivery parameters required by XNP_MESSAGE for outbound transmission.

Key Procedures and Functions

The package exposes five documented entry points:

• CREATE_MSG — Constructs the message header record and XML body for the T_DEF_JEOPARDY_TMR message type. It initializes the XML document via XNP_XML_UTILS, opens the T_DEF_JEOPARDY_TMR segment, and writes mandatory child elements such as DELAY and INTERVAL. Sender, recipient, version, reference, order, and workflow/FA instance identifiers are supplied by the caller. The routine raises a MISSING_MANDATORY_DATA exception when required attributes (for example, DELAY) are absent.
• PROCESS — Handles the inbound or full processing path for the message type, dispatching the assembled content to the appropriate XNP handlers.
• DEFAULT_PROCESS — Provides the standard, non-overridden processing behavior for the message, invoked when no specialized handler is registered.
• VALIDATE — Performs structural and business-rule validation of the message payload prior to dispatch or persistence.
• FIRE — Triggers the message dispatch, emitting the constructed XML header and body to the XNP messaging layer for delivery.

Tables Accessed

Per the documented metadata, the only table reference is DUAL, accessed through an APPS synonym. In CREATE_MSG, DUAL is used as a loop source (a single-iteration cursor returning 0 delay) to drive default handling and null-checking logic for the DELAY element. The business-interval value for the INTERVAL element is obtained through the package XNP_DEF_JEOPARDY_INT.get_interval, which encapsulates the underlying data retrieval rather than querying a base table directly. All remaining data dependencies are supplied by the caller as parameters, keeping the package free of direct table reads or writes.

Usage Notes

XNP_T_DEF_JEOPARDY_TMR_U is typically invoked indirectly through the XNP messaging framework rather than called directly from a form. Enqueueing of T_DEF_JEOPARDY_TMR messages is driven by order-management or supplier-scheduling flows that detect a jeopardy condition and invoke CREATE_MSG to build the payload, followed by VALIDATE and FIRE to transmit it. Because it is documented as referenced by one other package, callers should treat it as an internal messaging component and route invocations through that parent. For Oracle EBS 12.1.1 and 12.2.2, the package resides in the APPS schema with public synonym access and no separate grants are required. Customizations should avoid modifying the shipped source, as the file is patched at the 120.x level, and any extension should be implemented through wrapper packages to preserve supportability during upgrades.