Search Results p_schedule_rev




Overview

PO_CHVPRSCH_XMLP_PKG is the generated PL/SQL package that backs the Oracle E-Business Suite concurrent program "Vendor Scheduling Report" (short name CHVPRSCH, source file CHVPRSCHS.pls). It is a BI Publisher / XML Publisher report package, identified by the _XMLP_PKG suffix, that the Oracle Reports-to-XML Publisher conversion utility produces for reports run through the XML Publisher engine on release 12.1.1 and 12.2.2. The package performs no business logic of its own; instead it declares the report's input parameters as package globals, supplies the lexical and group filters the XML Publisher runtime needs to shape the query result set, and defines the before/after report hooks that execute around the data fetch.

Functionally, the package supports the Vendor Scheduling Report, which lists vendor scheduling agreements and their releases (schedules) as held in the CHV tables of Oracle Purchasing. It allows a planner or buyer to review schedule headers and lines across a horizon of dates, filtered by schedule number, schedule type, schedule subtype, revision, vendor name range, vendor site, and organization. The search term "p_schedule_num" maps directly to the package global P_schedule_num, the report parameter that restricts output to a single scheduling agreement number.

Key Procedures and Functions

The package exposes five documented program units in addition to its parameter globals:

  • BeforeReport — The standard XML Publisher before-report function. It executes once prior to the report query, and returns a boolean that controls whether report generation proceeds. It is the conventional place for initialization and any global setup.
  • get_precision — A procedure that resolves quantity precision for the report. It derives the precision setting used to format quantities in the output, storing the result in the package global P_qty_precision, typically sourced from the organization's inventory or unit-of-measure setup.
  • g_headersgroupfilter — A group filter function applied to the schedule headers group. It accepts a schedule identifier and returns a boolean, determining which CHV_SCHEDULE_HEADERS rows are included in the report data set. This is where header-level inclusion rules are enforced after the query returns rows.
  • addressformula — A formula function that accepts an organization identifier and returns a character value. It is used to produce the formatted address text for the vendor site or organization block of the report, drawing on location data.
  • AfterReport — The standard after-report function, invoked once after the data set is produced. It returns a boolean and is used for post-processing or cleanup.

Tables Accessed

Two tables are documented as referenced through APPS synonyms:

  • CHV_SCHEDULE_HEADERS — The Purchasing scheduling agreement header table. It is the report's primary source and the table against which the header group filter operates; it supplies schedule number, type, subtype, revision, and vendor identifiers.
  • HR_LOCATIONS_ALL — The Human Resources location table, used to resolve address and site details for the vendor site and delivering organization shown on the report, feeding the addressformula output.

The package is not documented as referenced by any other package, so it is a terminal report package rather than a shared utility.

Usage Notes

PO_CHVPRSCH_XMLP_PKG is invoked by the XML Publisher concurrent program runtime when the Vendor Scheduling Report is submitted, not by application forms or custom code. Users select it from the Purchasing responsibility's request submission or request set. Parameters presented to the user — including Schedule Number (P_schedule_num), Schedule Type (P_schedule_type), Schedule Subtype (P_schedule_sub), Schedule Revision (P_SCHEDULE_REV), Vendor Name From/To (P_vendor_name_from, P_vendor_name_to), Site (P_site), Horizon Start/End (P_horizon_start, P_horizon_end), Organization (P_organization_name, P_ORGANIZATION_ID), Test Print (P_test_print), Exclude Zero Quantity Lines (P_EXCLUDE_ZERO_QUANTITY_LINES), and Autoschedule Flag (P_AUTOSCHEDULE_FLAG) — are bound into the corresponding package globals at runtime. The Oracle Reports bridge populates P_CONC_REQUEST_ID and P_BATCH_ID as part of the standard concurrent request context. Because the package is regenerated from the report template, direct modification is not supported; changes must be made to the report definition and the package redeployed.