Search Results xnp_def_jeopardy_logic




Overview
Explore in AI Chat

Overview

The APPS.XNP_DEF_JEOPARDY_LOGIC package body is a component of the Oracle E-Business Suite (EBS) Transportation Management / ETRM module, catalogued under the XNP naming prefix that designates ETRM-process logic objects. Its purpose is to encapsulate the business rules that govern "jeopardy" conditions on orders — that is, circumstances in which an outbound order is at risk of missing its planned shipment or delivery window, and therefore requires escalation or notification. Rather than embedding this logic inside a form or a workflow process, Oracle centralizes the decision logic in this PL/SQL package so that it can be invoked consistently from multiple entry points across the application. The package is a VALID object owned by the APPS schema and is classified as a miscellaneous (OTHER) API rather than a formal public interface.

Key Procedures and Functions

The ETRM metadata documents a single callable program unit within this package body:

  • NOTIFY_FMC — The notification routine associated with order jeopardy processing. Its purpose is to alert the designated FMC (Freight Management Center) recipient when a jeopardy condition is detected or escalated. The procedure encapsulates the recipient resolution and message dispatch, delegating the actual message construction to the shared messaging utility XNP_MESSAGE and, where workflow-based notification is required, to the Oracle Workflow engine packages (WF_ENGINE and WF_CORE) that appear in the package dependency list.

No additional procedures or functions are documented for this package body in the ETRM 12.2.2 metadata, and no parameter lists are published in the repository. Readers requiring exact signatures should extract the source from the database using DBMS_METADATA or the ETRM "show dependent code" facility referenced in the dependency output.

Tables Accessed

The only table referenced by this package, through an APPS synonym, is:

  • XDP_ORDER_HEADERS — The ETRM order header table. Jeopardy evaluation is fundamentally order-centric, so the package reads order header records to identify the order context, dates, and attributes that drive the jeopardy determination and to supply substitution values used in the notification message.

The metadata records no insert, update, or delete activity against application tables from within this package. Message content is passed to XNP_MESSAGE, which owns the message persistence, and workflow orchestration is handled by the Workflow engine. This separation means the package remains a read-and-notify component rather than a transactional one.

Usage Notes

XNP_DEF_JEOPARDY_LOGIC is invoked indirectly rather than from a standard EBS form or concurrent program. The dependency report states that the package is referenced by one other package, confirming it is called as a subordinate utility within the ETRM jeopardy processing chain, most likely driven by a concurrent program or workflow background process that periodically scans orders for at-risk conditions. Its reliance on WF_ENGINE and WF_CORE indicates that notification may be routed through Oracle Workflow rather than a simple e-mail call. Because it is not referenced by any further database object and exposes no formally documented API contract, customizations that replace or extend this package carry upgrade risk; the recommended approach in 12.1.1 and 12.2.2 is to wrap or copy the logic into a custom package rather than modify the seeded body. Any change must be revalidated against the XDP_ORDER_HEADERS structure and the ETRM messaging APIs, since both remain hard dependencies of the compiled body.