Search Results cp_startdate_pp




Overview
Explore in AI Chat

Overview

APPS.PSB_PSBWSSUB_XMLP_PKG is a report-support package body in Oracle E-Business Suite that backs the "PSBWSSUB" XML Publisher (BI Publisher) concurrent program. The package belongs to the Public Sector Budgeting (PSB) product family and is classified under the ETRM API classification OTHER, indicating it is not a public, callable business API but rather an internal implementation artifact generated to support an Oracle Reports or XML Publisher report definition. In the 12.1.1 and 12.2.2 releases it resides in the APPS schema and is delivered as a noship object, as indicated by the header comment tag carried in the source ("$Header: PSBWSSUBB.pls 120.0 2008/01/07 ... noship $").

Its business purpose is to supply the report's BeforeReport, BeforePForm, AfterPForm, BetweenPage, and AfterReport trigger logic and to expose the report's parameter and computed-column values to the XML Publisher template. The package resolves a budget group name, a lookup meaning, calendar dates, and worksheet identifiers so the budget worksheet submission report can render the correct headings, date ranges, and worksheet context to the end user.

Key Procedures and Functions

The package implements the following report trigger entry points and parameter accessor functions:

  • BEFOREREPORT — Initializes the concurrent request context, derives the budget group name and the "not submitted only" lookup meaning, resolves the worksheet and budget calendar context, retrieves the calendar period start and current-year end dates, and sets message-derived values used by the report. It returns a Boolean success indicator to the report engine.
  • BEFOREPFORM — Report format/parameter-form trigger executed before the parameter form is displayed.
  • AFTERPFORM — Trigger executed after the parameter form is submitted and validated.
  • BETWEENPAGE — Trigger executed between report pages, commonly used for running totals or page-level setup.
  • AFTERREPORT — Trigger executed after report completion, used for final housekeeping or message retrieval.
  • CP_BUDGET_GROUP_NAME_P — Accessor returning the resolved budget group name derived from PSB_BUDGET_GROUPS.
  • CP_NO_DATA_FOUND_P — Accessor returning the localized "no data found" message text.
  • CP_END_OF_REPORT_P — Accessor returning the localized "end of report" message text.
  • CP_STARTDATE_PP_P — Accessor returning the prior-period start date computed from the budget calendar.
  • CP_ENDDATE_CY_P — Accessor returning the current-year end date computed from the budget calendar.
  • CP_NOT_SUBMITTED_ONLY_P — Accessor returning the meaning of the YES_NO lookup code supplied via the P_NOT_SUBMITTED_ONLY_FLAG parameter.
  • CP_GLOBAL_WORKSHEET_ID_P — Accessor returning the effective global worksheet identifier, which resolves to the global worksheet ID when the flag is 'Y', otherwise the entered worksheet ID.

Tables Accessed

Per ETRM metadata, the package references two PSB tables through APPS synonyms:

The package also reads the FND_LOOKUPS view for the YES_NO lookup type and invokes PSB_WS_ACCT1.GET_BUDGET_CALENDAR_INFO to derive the start and end dates. These supporting references are documented in the package source excerpt but are not listed among the APPS-synonym table dependencies in the ETRM record.

Usage Notes

PSB_PSBWSSUB_XMLP_PKG is invoked exclusively by the PSBWSSUB concurrent program and its XML Publisher/Reports definition. It is not registered as a callable API and is referenced by zero other packages per ETRM metadata. Triggers such as BEFOREREPORT are executed automatically by the report runtime when the concurrent request is submitted, and the CP_* accessor functions are called by the report layout to emit parameter and computed-column values.

Because the source header carries "120.0" and a 2008 file date, this object is a legacy Oracle Reports-style XMLP package that persists unchanged into 12.1.1 and 12.2.2. Customers may see it in the APPS schema when browsing report support packages, but it should not be modified directly; the EBS patching infrastructure derives it from the shipped .pls source file. The "noship" flag indicates the file is a source-control artifact rather than a runtime-shipped binary.