Results for “wip_wf_update_date”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

WIP_WF_UPDATE_DATE is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified in the ETRM repository under the generic API category OTHER. Its documented status is VALID, and it is deployed identically in release 12.1.1 and 12.2.2. The package name indicates its purpose: it supports date-maintenance operations within the Work in Process (WIP) and Workflow (WF) domain, specifically the controlled update of promise dates and need-by dates associated with manufacturing and procurement demand. In a discrete manufacturing environment, promise dates and need-by dates drive scheduling, material availability analysis, and supplier commitments. When these dates must be revised — because of capacity changes, component shortages, or customer-driven rescheduling — the change must propagate consistently across the affected Work in Process entities and the associated purchasing documents. WIP_WF_UPDATE_DATE encapsulates that propagation logic so that callers do not have to manipulate the underlying date columns directly. The package is also designed to participate in Oracle Workflow-driven processes, as evidenced by the STARTNBDWFPROCESS procedure, which suggests it can initiate a workflow process as part of a need-by date change cycle.

Key Procedures and Functions

The ETRM metadata documents four callable units within the package. No parameter signatures are published, so only their functional intent is described here.

• STARTNBDWFPROCESS — Initiates the Workflow process associated with a need-by date (NBD) change. This procedure is the entry point that ties the date update to the Workflow engine, ensuring notifications, approvals, or downstream activities are launched when a need-by date is modified.
• UPDATE_PROMISE_DATE — Performs the update of promise date values on the relevant WIP or purchasing records. This is the primary write operation for promise date maintenance.
• UPDATE_NEED_BY_DATE — Performs the corresponding update for need-by dates. Because need-by dates are tightly coupled to Workflow-driven rescheduling, this procedure is typically invoked alongside or through STARTNBDWFPROCESS.
• PROMISE_DATE — Functions as the promise date accessor, returning the current or calculated promise date value for the entity under consideration. It supports the update and workflow logic by providing a consistent read of the promise date.

Tables Accessed

The package accesses five documented base tables through APPS synonyms. MTL_SYSTEM_ITEMS_KFV is the key-flexfield view over the item master, used to resolve item attributes such as planning parameters that influence date validation. PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, and PO_DISTRIBUTIONS_ALL constitute the purchasing document hierarchy. Promise dates and need-by dates are stored at the line location and distribution levels in Oracle Purchasing, so the package reads and writes these tables to reflect revised dates on the affected shipments and distributions. The inclusion of the full purchasing hierarchy confirms that the package's date updates are not confined to WIP work orders but extend into the procurement commitments generated from them.

Usage Notes

WIP_WF_UPDATE_DATE is an internal utility package rather than a public, supported API. ETRM records that it references only SYS.STANDARD and is referenced by zero other packages, which indicates a narrow, self-contained dependency footprint. Its procedures are invoked in scenarios where promise or need-by dates on purchasing and WIP records must be revised programmatically — commonly from concurrent programs, Workflow background processes, or custom extensions that require coordinated date changes. Because the package is not exposed as a formal API and its parameters are undocumented, direct invocation from custom code should be undertaken only after reviewing the underlying package body. The APPS.WIP_WF_UPDATE_DATE object should be treated as a date-maintenance building block within the WIP and Purchasing integration, not as a general-purpose rescheduling interface.