Search Results default_process

Overview

The package APPS.XNP_T_DEF_JEOPARDY_TMR_U is a message-type handler within the Oracle E-Business Suite Advanced Supply Chain Planning and Order Management messaging infrastructure. It conforms to the ETRM (Event and Transaction Replication Model) pattern, in which each registered message type is implemented as a PL/SQL package that exposes a standardized set of entry points for creating, validating, processing, and firing messages. The suffix _U indicates a user-defined message type, and T_DEF_JEOPARDY_TMR corresponds to the default jeopardy timer message type.

Functionally, the package encapsulates the business logic required to notify trading partners, internal planners, or downstream processes when an order, work-in-process instance, or forecast instance is assessed to be in jeopardy of missing its scheduled date. The package is declared with AUTHID CURRENT_USER, meaning its SQL executes with the privileges of the invoking schema rather than its owner; callers must therefore possess direct grants on any objects referenced. The header comment records a creation/update revision dated 2006/02/13, reflecting its long-standing stability across the 12.1.1 and 12.2.2 code lines.

Key Procedures and Functions

• CREATE_MSG — Assembles a new message for the T_DEF_JEOPARDY_TMR message type. It returns a populated message header record and message text, along with error code and error message outputs, and accepts optional attributes such as sender name, recipient list, version, reference identifiers, order identifier, work-in-process instance identifier, forecast instance identifier, and delay/interval values.
• PROCESS — Executes the principal inbound processing logic for a jeopardy timer message that has been received. It consumes a message header and text, returning error code and error message, and optionally accepts a process reference for correlation.
• DEFAULT_PROCESS — Provides the default processing path for the message type, invoked when no specialized handling is required. It is the entry point referenced in the user's search for "default_process."
• VALIDATE — Performs validation of the message header and text prior to processing. Because the header parameter is IN OUT NOCOPY, validation may amend or normalize header attributes in place, and returns error code and error message outputs.
• FIRE — Initiates the message event, returning a timer identifier and timer contents together with error code and error message. It accepts optional sender, recipient, version, reference, order, WIP instance, and forecast instance parameters, mirroring the event attributes used by CREATE_MSG.

Tables Accessed

The documented metadata identifies only DUAL as a referenced table, accessed through an APPS synonym. This indicates that the package's documented logic performs no direct persistent read or write operations against application base tables; instead, all data is exchanged through the message header record type and the message text parameter supplied by the ETRM runtime. Persistent state, correlation identifiers, and event attributes are carried by XNP_MESSAGE.MSG_HEADER_REC_TYPE and by the timer services that invoke FIRE.

Usage Notes

Packages of this class are not typically called directly by end users. Instead, they are registered with the ETRM message framework, which dispatches calls to CREATE_MSG, VALIDATE, PROCESS, DEFAULT_PROCESS, and FIRE based on the lifecycle stage of a message. Custom code may invoke the package directly when constructing jeopardy timer notifications programmatically, for example from Order Management or Advanced Planning concurrent programs that detect late or at-risk supply. Because the package is referenced by one other package, integrators should treat it as a dependency-sensitive component and verify behavior after upgrades between 12.1.1 and 12.2.2, particularly where AUTHID CURRENT_USER requires explicit object privileges for the calling schema.