Search Results p_where_clause1

Overview

RLM_RLMDPDER_XMLP_PKG is an Oracle E-Business Suite report logic package body owned by the APPS schema. It encapsulates the server-side PL/SQL logic associated with an Oracle Reports executable generated from an XML Publisher (XMLP) definition, consistent with Oracle EBS 12.1.1 and 12.2.2 conventions where report packages are named after the underlying report definition. The package is classified under ETRM as OTHER, indicating it is a report-support unit rather than a public application programming interface. Its primary purpose is to prepare report parameters and derived context at run time, most notably organizational access context, date range formatting, and dynamic WHERE clause construction for the report query.

The p_where_clause1 parameter that prompted the search is handled directly in this package: the BEFOREREPORT function initializes P_WHERE_CLAUSE1 to a single space when it is null, ensuring the concatenated SQL fragment remains syntactically valid. This confirms that p_where_clause1 is one of the reserved report parameters used to accept externally supplied predicate fragments and that the package is the authoritative place where its defaulting occurs.

Key Procedures and Functions

• BETWEENPAGE — Returns a boolean indicating whether logic should execute between report pages. In the documented body it returns TRUE unconditionally, effectively a stub placeholder.
• BEFOREPFORM — Boolean function invoked before the report form/parameter form is displayed. Documented body returns TRUE, serving as a no-op hook.
• BEFOREREPORT — The principal initialization routine. It captures FND_GLOBAL.CONC_REQUEST_ID, resolves the current operating unit via MO_GLOBAL.GET_CURRENT_ORG_ID, sets policy context through MO_GLOBAL.SET_POLICY_CONTEXT when needed, derives the operating unit name with FND_ACCESS_CONTROL_UTIL.GET_ORG_NAME, formats date bounds, and defaults and builds the P_WHERE_CLAUSE, P_WHERE_CLAUSE1, and P_WHERE_CLAUSE2 fragments.
• CF_QUANTITY_TYPEFORMULA — Column-level formula for the quantity type field, feeding the report layout.
• CF_ITEM_DETAIL_TYPEFORMULA — Column-level formula for item detail type presentation.
• CF_ITEM_DETAIL_SUBTYPEFORMULA — Column-level formula for item detail subtype presentation.
• CF_ORDER_TYPEFORMULA — Column-level formula for order type.
• CF_SCHEDULE_TYPEFORMULA — Column-level formula for schedule type.
• CF_SCHEDULE_PURPOSEFORMULA — Column-level formula for schedule purpose.
• CF_SCHEDULE_SOURCEFORMULA — Column-level formula for schedule source.
• AFTERREPORT — Post-report routine, typically used to release context or finalize state after data retrieval.
• CP_DEFAULT_OU_P — Getter/accessor returning the cached default operating unit name (CP_DEFAULT_OU).
• CP_ORG_ID_P — Getter/accessor returning the cached organization identifier (CP_ORG_ID).

Tables Accessed

The supplied ETRM metadata records no direct table references through APPS synonyms for this package. In practice, the substantive data access occurs in the associated Oracle Reports query, which consumes the dynamically assembled WHERE clause; the package itself primarily performs API-based lookups such as request ID resolution, organization access checks, and operating unit name retrieval rather than issuing DML against application tables.

Usage Notes

The package is invoked by the Oracle Reports runtime for the associated RLM report executable, not by application forms directly. BEFOREREPORT and AFTERREPORT fire automatically as report triggers, while the CF_* formulas are evaluated per row during formatting. It is referenced by zero other PL/SQL packages, so it has no inbound programmatic dependency and should be treated as report-private. Customizations that need to alter default predicate behavior should target the report's parameter form or the underlying query rather than modifying this package, since it is a seeded object under the APPS schema. The p_where_clause1 parameter is defaulted here to a single space when null, so any consumer of that parameter can assume a non-null value after BEFOREREPORT completes.