Search Results p_seeded

Overview

The PL/SQL package body APPS.ONT_OEXDERUL_XMLP_PKG is the implementation unit behind a seeded Oracle Order Management XML Publisher (BI Publisher) report, identified by the _XMLP_PKG naming convention shared across EBS 12.1.1 and 12.2.2. The ONT prefix places it within the Order Management (Order Capture/Order Fulfillment) module, while the OEXDERUL fragment denotes an Order Entry "Detail Rules" or "Order Entry Rule" report seeded against the OM reporting framework. In practice this package serves as the data-model engine that the XML Publisher concurrent program calls to fetch the report's XML output, populate global report attributes such as the report name, subtitle, object and attribute names, and condition driving the extract, and hand control back to the concurrent manager. Its status is VALID in the ETRM registry, and the package is classified as OTHER in 12.2.2 documentation, meaning it is a report-support package rather than a public API.

Key Procedures and Functions

Eleven documented procedures and functions are exposed by the package. The four report lifecycle hooks are BEFOREREPORT, AFTERREPORT, and AFTERPFORM, which execute before report execution, after report completion, and after the parameter form is submitted, respectively, together with SOURCEVALUEFORMULA which supplies a value derived from the report source for use in the layout or parameter logic. A set of report-context accessors provide the XML Publisher runtime with metadata: RP_REPORT_NAME_P returns the report name, RP_SUB_TITLE_P returns the report's subtitle, RP_DATA_FOUND_P indicates whether the query produced rows, RP_CONDITION_P exposes the condition used to filter the extract, and RP_OBJECT_P, RP_ATTRIBUTE_P, and RP_SEEDED_P return the object name, attribute name, and seeded flag used to describe the rule/attribute metadata being reported. Naming aside, none of these appear in the reference metadata with parameter lists, so each is treated as a no-argument accessor or trigger executed by the report engine.

Tables Accessed

The package does not query application tables directly; instead it reads through the OM reporting framework. The documented dependency on FND_CONCURRENT_REQUESTS (via APPS synonym) is used to retrieve the current concurrent request context, while FND_CONCURRENT_PROGRAMS_VL supplies the concurrent program definition and FND_GLOBAL provides runtime session information such as responsibility, user, and application. The transaction and rule data itself is sourced through the report owner's views: OE_DEF_AK_ATTR_EXT_V and OE_DEF_AK_OBJ_EXT_V for attribute/object extension definitions, and OE_DEF_CONDITIONS_VL for condition definitions. Shared logic is reused from OM_REPORTS_COMMON_PKG, and the package reports no inbound referencing database objects, confirming it is a leaf consumer.

Usage Notes

This package is invoked exclusively by Oracle's seeded XML Publisher concurrent program for the Order Entry Rule report. Administrators run the report from the Concurrent Requests or Submit Request forms in Order Management, or via the Reports and Requests menu in the Oracle Applications framework; the concurrent manager calls the package to build the XML payload, then XML Publisher applies the seeded template. Because the package is not referenced by any other object and is documented as OTHER, it is not a supported extension point. Customizations should be applied to the XML Publisher template or the underlying data definition rather than to this package body, and the package should not be modified directly, as patch application in 12.1.1 and 12.2.2 will overwrite such changes. Developers who need equivalent data should call OM_REPORTS_COMMON_PKG or query the OE_DEF_* views directly.