Results for “update_need_by_date”

20 results




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

Overview

PO_UPDATE_DATE_PKG is a small utility package in the Oracle E-Business Suite Purchasing module (APPS schema) whose sole purpose is to perform targeted, single-row date updates on purchasing documents. It is a low-level data maintenance package rather than a full business API: it contains no validation logic, no workflow integration, and no attribute-derivation routines. Each procedure accepts an identifier plus a new date value, executes a single UPDATE against the relevant purchasing table, and issues an explicit COMMIT.

The package header line, dated 1999, indicates that the package has been part of the Purchasing codebase since the earliest releases and has been carried forward unchanged into EBS 12.1.1 and 12.2.2. Its persistence across releases reflects its use as an internal convenience routine for date-only maintenance, distinct from the larger PO_* APIs used for controlled document changes.

Key Procedures and Functions

  • UPDATE_PROMISED_DATE — Updates the promised date on a purchasing document line location. The procedure takes a line location identifier and a new promised date, and is used when the supplier-committed date on a shipment or distribution must be corrected or advanced.
  • UPDATE_NEED_BY_DATE — Updates the need-by date on a purchasing document line location. This is the procedure most frequently associated with the search term "update_need_by_date." The need-by date represents the date by which the buying organization requires delivery, and this procedure rewrites that value directly on the line location record.
  • UPDATE_REQ_NEED_BY_DATE — Updates the need-by date on a requisition line rather than a purchase order line location. It mirrors UPDATE_NEED_BY_DATE but targets the requisition side of the procurement flow, allowing the requested need-by date to be adjusted after requisition entry or approval.

All three procedures are exposed in the package specification and are callable as APPS-schema procedures. None return a status value or raise application-defined errors; the metadata documents no OUT parameters or exception handlers.

Tables Accessed

  • PO_LINE_LOCATIONS_ALL — The shipment and distribution table for purchase orders, blanket agreements, and contracts. UPDATE_PROMISED_DATE and UPDATE_NEED_BY_DATE both target this table, keyed by LINE_LOCATION_ID. The _ALL suffix confirms that records are not filtered by operating unit, so the procedures operate on the identified row irrespective of org context.
  • PO_REQUISITION_LINES_ALL — The requisition line table in Purchasing. UPDATE_REQ_NEED_BY_DATE writes the NEED_BY_DATE column here, keyed by REQUISITION_LINE_ID.

Both tables are referenced through APPS synonyms, consistent with standard EBS coding practice. The package performs no SELECT statements and reads no configuration or control tables.

Usage Notes

Because the procedures contain only an UPDATE and a COMMIT, they are typically invoked from Purchasing forms, from other PL/SQL packages in the same schema, or from custom correction scripts. The ETRM metadata records the package as being referenced by one other package, indicating internal reuse within the Purchasing module's PL/SQL layer.

Several operational cautions apply. The unconditional COMMIT inside each procedure ends the calling transaction, so the package should not be called from within a larger unit of work that requires atomic rollback. No validation is performed against the document's approval status, open/closed state, or any change-management rules, and no audit or history rows are written. Direct invocation therefore bypasses the business logic that normally governs date changes on purchasing documents and should be restricted to controlled maintenance scenarios.