Search Results jtf_diag_report




Overview
Explore in AI Chat

Overview

WIP_DIAG_WOL_FLOW is a diagnostic PL/SQL package owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the family of Oracle Diagnostics (formerly "Diagnostics") test packages that populate the Oracle Applications Diagnostics framework, whose test definitions and results are stored and surfaced through the JTF_DIAG tables. As the name indicates, WIP_DIAG_WOL_FLOW addresses Work in Process (WIP) Work Order-less (WOL) transactions — discrete manufacturing material and resource movements that occur without a formal work order — a scenario common in process, repetitive, and flow-style shops where inventory and resource charges are posted directly rather than through a defined job.

The package was created with AUTHID CURRENT_USER, meaning it executes under the privileges of the invoking user rather than the definer, which is the standard convention for diagnostic test packages in the Oracle Applications Diagnostics framework. Its header (WIPDWOLS.pls, version 120.0.12000000.1, dated 2007/07/10) confirms an unmodified, Oracle-shipped diagnostic utility.

Key Procedures and Functions

Four procedures are documented, all of which share the Diagnostics framework signature — an IN parameter of type JTF_DIAG_INPUTTBL for test inputs, plus OUT parameters of type JTF_DIAG_REPORT and CLOB for the structured and large-object report output:

  • UNCOSTED_MAT_TXN_WOL — Identifies WOL material transactions that remain uncosted. These represent inventory issues and returns that have not been picked up by the Cost Management (CM) cost worker, causing variances between subledger and general ledger balances.
  • PENDING_RES_TXN_WOL — Detects resource transactions associated with WOL activity that are still pending costing. Pending resource charges can leave WIP and resource balances overstated until the cost worker processes them.
  • INVALID_TXN_MTI_WOL — Flags invalid Material Transaction Interface (MTI) rows tied to WOL transactions, useful in isolating records that failed validation in the transaction processor.
  • DUP_MAT_TXN_MTI — Reports duplicate material transaction interface records, a frequent cause of double-charged inventory or costing discrepancies.

Tables Accessed

The ETRM metadata for this package does not enumerate specific base tables accessed via APPS synonyms, which is typical for diagnostic packages that query costing and transaction interface tables dynamically. Based on the documented procedure purposes, the package logically interrogates WIP and Cost Management transaction interface structures — MTI (Material Transaction Interface) and resource transaction interface tables — together with the standard JTF_DIAG framework tables that hold input parameters and formatted diagnostic report output. All access is performed through APPS synonyms under the invoking user's privileges.

Usage Notes

The package is not intended for direct invocation by end users or custom applications. It is executed by the Oracle Applications Diagnostics concurrent programs or by the Diagnostics test runner when the user runs the "WIP Work Order-less Flow" diagnostic on a target instance. The user search term "jtf_diag_report" reflects this — JTF_DIAG_REPORT is the report OUT parameter type that carries the formatted results back into the Diagnostics UI and the underlying JTF_DIAG tables. The metadata states the package is referenced by four other packages, consistent with a diagnostic test being registered and chained by peer diagnostics modules. Support and DBA staff invoke it during troubleshooting of WIP costing, inventory valuation, and interface failures in a WOL manufacturing environment.