Search Results cf_status

Overview

The APPS.RLM_RLMDPPSR_XMLP_PKG package is the generated PL/SQL specification that backs an Oracle XML Publisher (BI Publisher) concurrent program report within the Oracle E-Business Suite Release 12.1.1 / 12.2.2 environment. The package name follows the standard XML Publisher package naming convention, in which the _XMLP_PKG suffix is appended to the base report short name RLMDPPSR. The RLM prefix associates the package with the Oracle Release Management (RLM) product family, and the report logic relates to demand scheduling and demand exception processing. The package serves as the server-side anchor for the report: it declares the bind and lexical parameters supplied by the concurrent program, exposes PL/SQL formula functions invoked by the report template, and provides the before-report and after-report program units that XML Publisher calls during report execution.

The package was last modified under version 120.1 per the embedded header, dated 2008/01/25, and is owned by the APPS schema. It is classified as OTHER in the API taxonomy, meaning it is not a public integration API but rather an internal report implementation package.

Key Procedures and Functions

The specification documents eighteen program units. The two lifecycle functions are BEFOREREPORT, which performs setup work before the XML data model is executed, and AFTERREPORT, which performs cleanup or post-processing after report completion. The bulk of the remaining units are XML Publisher formula columns, each named for the query column or display element it derives. These include CF_SCHEDULE_TYPEFORMULA and CF_P_SCHED_TYPEFORMULA for schedule type display, CF_PURGE_STATUSFORMULA and CF_PURGE_ELIGIBLEFORMULA for purge-related status logic, CF_EXECUTIONFORMULA for execution mode formatting, CF_YES_NOFORMULA for boolean-style rendering, CF_STATUS and CF_CUSTOMERFORMULA for status and customer presentation, and CF_SHIP_TO_TOFORMULA for ship-to address display. Numeric and auxiliary formulas include CF_1FORMULA, CF_COUNT2FORMULA, CF_COUNT3FORMULA, CF_1FORMULA0006, and CF_1FORMULA0004.

Two accessor and trigger units are notable. CP_DEFAULT_OU_P is the accessor function for the package-level variable CP_DEFAULT_OU. This is the object that corresponds to the user's search term cp_default_ou_p: it returns the operating unit context for the report run, allowing the report template and data model to resolve the correct default operating unit. M_2FORMATTRIGGER is a format trigger whose name derives from the M_2 variable. The package-level variables, including P_SCHEDULE_TYPE, P_SCHEDULE_REF_NO, P_AUTHORIZATION, P_REQUEST_ID, P_CONC_REQUEST_ID, P_ORG_ID, P_CUSTOMER, P_STATUS, and the date and ID range parameters, are populated by the concurrent program and consumed by the formulas.

Tables Accessed

The package operates against four documented tables, all referenced through APPS synonyms. RLM_DEMAND_EXCEPTIONS is the core RLM table holding demand exception records, and the report's schedule, purge, and status formulas derive from its contents. HZ_CUST_ACCOUNTS and HZ_CUST_ACCT_SITES supply customer account and account site data used by CF_CUSTOMERFORMULA and CF_SHIP_TO_TOFORMULA. HZ_PARTIES provides the party-level attributes underlying customer identification and naming. No other database objects are documented as referenced by this package.

Usage Notes

This package is invoked indirectly by the XML Publisher concurrent program associated with the RLMDPPSR report; it is not intended for direct invocation from a form or by external custom code. It is referenced by zero other packages, confirming its role as a leaf-level report implementation unit. Administrators and developers typically encounter it when diagnosing a concurrent request, tracing an operating unit resolution issue through CP_DEFAULT_OU_P, or troubleshooting a report template that calls one of the CF_*FORMULA functions. Because the package is regenerated by the XML Publisher report definition tooling, manual modifications are overwritten and should be avoided; customization belongs in the report definition or a copied package.