Search Results cf_item_detail_typeformula




Overview
Explore in AI Chat

Overview

The APPS.RLM_RLMDPDER_XMLP_PKG package is the generated PL/SQL package body that supports an Oracle EBS Reports (Oracle Report / XML Publisher) executable within the Release Management (RLM) module. RLM provides the Order Management supply-chain functionality associated with shipping, receiving, and trading-partner collaboration. The package name follows the standard EBS convention for form/report packages: the _XMLP_PKG suffix indicates that the underlying report is executed through the XML Publisher engine and that this package is the PL/SQL container that wires report parameters to the SQL query and the layout engine.

Its primary business function is to accept the runtime parameters entered on the report submission page, provide the AFTERPFORM/BEFOREREPORT triggers used by Oracle Reports to construct a dynamic WHERE clause, and supply the formula columns exposed on the report layout. The P_* global variables define the report's parameter surface — request ID range, order number range, exception severity, customer range, order type range, ship-from organization, trading partner, schedule number range, message category range, creation date range and so on — while the function block contains the logic used to render the report and to populate the lexical parameters that drive the query.

Key Procedures and Functions

The documented PL/SQL entry points comprise the standard Oracle Reports package interface plus a set of formula columns:

  • CP_ORG_ID_P and CP_DEFAULT_OU_P — These are the formula-column functions for the report parameters CP_ORG_ID and CP_DEFAULT_OU. They return the operating unit context used to restrict the report's data, which is the reason these names appear in the ETRM metadata and in the user's search for "cp_org_id_p". They translate the current report environment into the organization/OU identifier consumed by the report query.
  • BEFOREPFORM — Executed before the report's parameter form is displayed; typically used to initialise the parameter globals and default values before the user sees the form.
  • BETWEENPAGE — Executed between the logical pages of the report; used to reset or advance session-level state as the report paginates.
  • BEFOREREPORT — Executed immediately before the main report query runs; this is where the P_WHERE_CLAUSE, P_WHERE_CLAUSE1, P_WHERE_CLAUSE2, and the sort/order-by globals (P_SORT_BY, P_SORT_BY1, P_SORT_BY2, P_ORDER_BY, P_ORDER_BY1, P_ORDER_BY2) are assembled from the user's parameter selections.
  • AFTERREPORT — Executed after the report completes; used for cleanup and for returning final status to the concurrent manager.
  • CF_QUANTITY_TYPEFORMULA, CF_ITEM_DETAIL_TYPEFORMULA, CF_ITEM_DETAIL_SUBTYPEFORMULA, CF_ORDER_TYPEFORMULA, CF_SCHEDULE_TYPEFORMULA, CF_SCHEDULE_PURPOSEFORMULA, CF_SCHEDULE_SOURCEFORMULA — These are the layout formula columns of the report. Each accepts a coded value from the query (quantity type code, item detail type/subtype, order type id, schedule type, schedule purpose, schedule source) and returns its user-facing descriptive text, providing the translation layer between the base tables and the printed output.

Tables Accessed

The ETRM metadata excerpt does not enumerate specific base tables because the report query is embedded in the Oracle Reports .rdf definition and typically references public synonyms and views rather than base tables directly from the package. In the RLM/Order Management domain, the report supporting this package reads from order and schedule data — order headers, order lines, trading-partner and customer records, schedule headers and schedule lines, and the exception or message records used for the severity and message-category parameters. All access occurs through APPS-qualified synonyms, so no direct schema dependency is recorded. The package itself does not insert, update or delete data; it is read-only.

Usage Notes

This package is not a public API and is not referenced by any other documented package (Referenced by 0). It is invoked exclusively by its companion Oracle Report executable through the XML Publisher/Concurrent Manager runtime. Typical usage is a user submitting the associated RLM report from the Concurrent Programs window or from a related form function; the Application Object Library instantiates the package, populates P_CONC_REQUEST_ID, calls BEFOREPFORM, BEFOREREPORT, the formula columns, BETWEENPAGE and AFTERREPORT in sequence, and returns the formatted output. Because the parameter surface includes P_ORG_ID, CP_ORG_ID and CP_DEFAULT_OU, submissions should be made from a responsibility with an operating unit context; the MULTI-ORG enforcement relies on these values being populated correctly. Customisations should not call these functions directly — the supported extension point is the underlying report definition, and any change to the parameter list must keep the P_* globals in sync with the concurrent program parameters defined in the AOL setup.