Search Results wip_close_mgr




Overview
Explore in AI Chat

Overview

WIP_JOBCLOSE_PRIV is a private PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the OTHER API category. Its business purpose is to support the Oracle Work in Process (WIP) job close process by selecting, validating, and closing eligible discrete jobs. The package encapsulates the core job-closure logic invoked by the Close Manager interface, exposing a set of procedures that accept range-based selection criteria so that users can close jobs in controlled batches rather than one at a time.

The package name in the header comment, wip_jobclose_priv, confirms its private nature: it is not intended as a public, customer-callable API and exposes no AOL-registered public interface. It is called internally by EBS components such as the WIP Close Manager form and its associated concurrent programs. Because it is private, Oracle does not document it as a supported integration point, and the package signature may change between releases without notice.

In Oracle EBS 12.1.1 and 12.2.2, WIP_JOBCLOSE_PRIV remains part of the manufacturing execution stack, working alongside standard job-close concurrent programs (for example, the WIP Mass Close Jobs process) to deliver the same closure behavior programmatically.

Key Procedures and Functions

  • WIP_CLOSE_MGR — The primary documented procedure. Its stated purpose is to create an executable that is called from Close Manager. It drives the close process across a user-defined selection of jobs. Documented parameters govern the organizational context (organization ID), accounting class type (such as Standard Discrete, Asset Non-Standard, Expense Non-Standard), and a from/to range for accounting classes. Additional ranges restrict the closure set by job number, job release date, job start date, and job completion date. A job status parameter filters by states such as RELEASED, COMPLETE, COMPLETE NO CHARGES, ON HOLD, and FAILED CLOSE. Grouping is handled through a group identifier in WIP_DJ_CLOSE_TEMP, with flags to exclude reserved jobs and jobs with pending transactions. Report output is controlled by a report type (SUMMARY, NO REPORT, DETAIL USING PLANNED START QUANTITY, and similar), and an actual close date parameter supplies the closure date. Standard concurrent-program return values are used: errbuf for error messages and retcode, where 0 indicates success, 1 a warning, and 2 an error.
  • WIP_CLOSE — The second documented procedure. It performs the actual close operation against the jobs identified by the calling logic, applying the criteria assembled by WIP_CLOSE_MGR. Together the two procedures separate job selection from job closure execution.

Tables Accessed

WIP_JOBCLOSE_PRIV references a broad set of APPS synonyms spanning manufacturing, costing, purchasing, order management, and installation tables. The principal manufacturing tables are MTL_MATERIAL_TRANSACTIONS, MTL_MATERIAL_TRANSACTIONS_TEMP, MTL_RESERVATIONS, and MTL_TXN_REQUEST_LINES, used to evaluate pending material activity and reservations before a job may close. MTL_PARAMETERS and ORG_ACCT_PERIODS supply organization and open-period validation, while GL_LEDGERS and HR_ORGANIZATION_INFORMATION provide ledger and organization context.

Order and procurement references include MTL_SALES_ORDERS, OE_ORDER_LINES_ALL, PO_HEADERS_ALL, PO_LINE_LOCATIONS_ALL, and PO_DISTRIBUTIONS_ALL, which support valuation and linkage of jobs to sales orders and purchase commitments. CSI_ITEM_INSTANCES and CSI_II_RELATIONSHIPS are consulted for installed-base relationships. Collectively these accesses ensure that a job is only closed when its material, costing, and interface dependencies are resolved.

Usage Notes

WIP_JOBCLOSE_PRIV is invoked indirectly. Typical entry points are the WIP Close Manager interface and the WIP Mass Close Jobs concurrent program, both of which supply the parameter values described above. It is not registered as a public API and is not referenced by any other documented package, so custom code should not call it directly; use the supported public WIP job-close APIs and concurrent programs instead. When troubleshooting close failures (for example, jobs stuck in FAILED CLOSE), review the retcode and errbuf output, the pending-transaction and reservation exclusion flags, and the open accounting period, since these are the principal gating conditions enforced by the package.