Search Results g_exception_infogroupfilter




Overview
Explore in AI Chat

Overview

WIP_WIPPURGE_XMLP_PKG is the report logic package body that supports the WIP Discrete Purge report in Oracle E-Business Suite. It provides the PL/SQL backbone for an Oracle Reports (XML Publisher / SRW-based) concurrent program that purges obsolete discrete work in process (WIP) job and transaction data. The package orchestrates validation of the reporting organization, transformation of the user-supplied cutoff date into the correct time zone, evaluation of accounting period close status, and finally invocation of the underlying purge engine. It is owned by the APPS schema and classified as an OTHER API, indicating that it is intended primarily for internal use by the associated report rather than as a general-purpose integration interface.

The name suffix _XMLP_PKG reflects the Oracle Reports/XML Publisher generated package pattern. The package appears in the ETRM 12.2.2 metadata with eight documented procedures and functions, and it references the ORG_ACCT_PERIODS and WIP_TEMP_REPORTS tables through APPS synonyms.

Key Procedures and Functions

The package exposes the standard report lifecycle hooks together with specialized group filters and the purge driver:

  • BEFOREREPORT — The primary initialization and validation routine. It resolves the operating organization via WSMPUTIL.CHECK_WSM_ORG, captures the concurrent request identifier through FND_GLOBAL.CONC_REQUEST_ID, initializes the time zone using WIP_DISCRETE_WS_MOVE.INITTIMEZONE, and converts the cutoff date from server to client representation for display. It queries ORG_ACCT_PERIODS to determine the maximum closed period date and raises a formatted error (WIP_BAD_CUTOFF_DATE) when the cutoff is null or exceeds that boundary. When validation succeeds, BEFOREREPORT calls WIP_WICTPG.PURGE, passing the purge parameters and the various flag options for configuration, header, detail, move transaction, and cost transaction handling.
  • AFTERREPORT — Performs post-report cleanup and finalization at the conclusion of report execution.
  • AFTERPFORM — Executes after the parameter form is processed, allowing derived parameter values to be finalized before the main report query.
  • G_JOB_LINE_TABGROUPFILTER and G_JOB_LINE_INFOGROUPFILTER — Group filters applied to the job/line tabular and informational groups, controlling which rows are displayed in the report output.
  • G_EXCEPTION_INFOGROUPFILTER and G_SUCCESS_INFOGROUPFILTER — Group filters that separate exception records from successfully purged records, enabling the report to present both outcome categories.
  • PURGE — The public entry point that drives the purge operation, delegating the substantive deletion work to the WIP_WICTPG package while surfacing error number and error text parameters.

Tables Accessed

The package references two documented tables:

  • ORG_ACCT_PERIODS — Read in BEFOREREPORT to retrieve the latest closed accounting period's schedule close date for the specified organization. This value establishes the maximum permissible cutoff date and prevents purging activity within an open or unclosed period.
  • WIP_TEMP_REPORTS — The temporary reporting table that stores intermediate results, including success and exception rows produced during the purge, for retrieval by the report group filters and final output layout.

Additional dependencies include WIP_DISCRETE_WS_MOVE (time zone conversion helpers), WSMPUTIL (organization validation), WIP_WICTPG (purge engine), and FND_GLOBAL / FND_MESSAGE for concurrent request and message handling.

Usage Notes

This package is not designed for direct invocation by external applications. It is executed automatically when the WIP Discrete Purge concurrent program or its associated report is run from the Submit Requests form or an equivalent scheduling interface. The concurrent manager supplies the organization identifier, cutoff date, purge type, job range, item, line, and option parameters, along with the disposition flags that determine whether configuration, header, detail, move transaction, and cost transaction records are removed.

The parameter referenced in the user's search, p_report_option, controls the report's output disposition — typically whether the program runs in report-only, purge-only, or combined mode. Because the package body is version-controlled under a ship-header (the script shows a 2008 revision), implementers customizing this logic should copy it to a custom package and redirect the report definition rather than modifying the APPS-owned object in place, ensuring Oracle update patches are not invalidated. The validation performed in BEFOREREPORT means any invocation must supply a valid, closeable cutoff date; otherwise the package routes a descriptive error text (APP-25002) into the report and suppresses the purge entirely.