Results for “promise_date”

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

Overview

WIP_WF_UPDATE_DATE is an Oracle Workflow integration package in the Oracle E-Business Suite Applications (APPS) schema. Its business purpose is to initiate and manage the Oracle Workflow process that governs changes to need-by dates and promise dates on work orders and associated outside processing (OSP) purchase order documentation. When a planner, buyer, or manufacturing user modifies a need-by date or promise date within Oracle Manufacturing or Oracle Purchasing, this package resolves the relevant identifiers into human-readable names and launches the corresponding workflow, which routes notifications and approvals to the appropriate responsible parties.

The package body carries a header date stamp of 2003/09/11 and is classified under ETRM as an OTHER API type. It is not a public, general-purpose API in the same sense as an open interface or a standard business object API; rather, it is a specialized workflow trigger invoked from specific product flows. The source comment at the top of the body states that the procedure passes in IDs from the web tier and resolves names within the package, indicating that it is designed to accept surrogate keys from a web-based or forms-based front end and translate them into descriptive values before the workflow engine creates process instances.

Key Procedures and Functions

Four documented procedures and functions constitute the package interface.

• STARTNBDWFPROCESS — Initiates the need-by-date change workflow. It accepts a workflow item type, an item key, and a workflow process name, then calls WF_ENGINE.CREATE_PROCESS to instantiate the workflow. It resolves the OSP item number and description from purchasing and inventory tables and gathers supporting purchase order data before the process is launched.
• UPDATE_PROMISE_DATE — Handles the update of a promise date and drives the associated workflow activity. It is the entry point used when the promise date, rather than the need-by date, is modified.
• UPDATE_NEED_BY_DATE — Handles the update of a need-by date on a work order or related document and initiates the corresponding change workflow.
• PROMISE_DATE — A function associated with promise date processing, providing date retrieval or validation logic used by the workflow.

The item_key parameter referenced in the user search maps directly to the Oracle Workflow item key, the unique identifier that ties a workflow process instance to its source business object. STARTNBDWFPROCESS declares item_key as an input parameter and passes it to WF_ENGINE.CREATE_PROCESS, ensuring each need-by-date change is tracked as a discrete workflow instance.

Tables Accessed

The package reads from the following APPS synonyms:

• PO_DISTRIBUTIONS_ALL — Supplies distribution-level detail linking purchase order lines to the OSP transaction; used to resolve item and description.
• PO_LINES_ALL — Provides the item identifier and item description for the OSP line.
• PO_HEADERS_ALL — Supplies header-level purchase order attributes needed for the workflow payload.
• PO_LINE_LOCATIONS_ALL — Provides shipment and line location identifiers.
• MTL_SYSTEM_ITEMS_KFV — The key flexfield view used to obtain the concatenated item segment (item number) and organization-specific item attributes.

None of the documented tables are written to by this package; it is a read-only consumer of purchasing and inventory data whose primary output is a workflow process instance.

Usage Notes

WIP_WF_UPDATE_DATE is invoked from Oracle Manufacturing and Oracle Purchasing forms or web pages when a user changes a need-by or promise date. The source comment confirms that it receives IDs from the web tier and resolves names internally, so callers are expected to pass identifiers such as WIP_ENTITY_ID, ORGANIZATION_ID, PO_DISTRIBUTION_ID, and PO_NUMBER rather than descriptive text. The ETRM metadata records zero packages referencing it, indicating it is a top-level entry point rather than a shared utility. Customizations should not call this package directly unless replicating the standard date-change workflow, because the workflow item type and process name must match the seeded definitions. Any modification should preserve the item_key contract, since workflow instance integrity depends on the unique item key supplied by the caller.