Search Results chv_schedule_items_pkg_s1




Overview
Explore in AI Chat

Overview

The package body APPS.CHV_SCHEDULE_ITEMS_PKG_S1 supports the Oracle EBS supplier scheduling and purchasing scheduling functionality, operating against scheduling agreement data maintained in the CHV_SCHEDULE_ITEMS table. In Oracle EBS 12.1.1 and 12.2.2, this table holds the item-level detail for schedules — cumulative quantities, authorization quantities, planning methods, purchasing and primary unit of measure references, and the buyer/item associations used by the scheduling and receipt-confirmation processes. This package body is designated an API of classification OTHER by the ETRM metadata, meaning it is treated as a supporting (often form-generated) server-side implementation rather than a public, published API. Its primary business role is to provide row-level locking and validation against CHV_SCHEDULE_ITEMS so that concurrent users modifying schedule lines through the Oracle Forms interface receive consistent optimistic-locking behavior rather than silent data overwrite.

Key Procedures and Functions

The ETRM metadata records four documented procedures or functions whose names are the identifier NAME; the source excerpt provided confirms the implementation of Lock_Row. Based on the documented source, the relevant program units are:

  • lock_row — the principal documented procedure. It accepts a row identifier (X_Rowid) plus the full set of CHV_SCHEDULE_ITEMS column values (schedule ID, schedule item ID, organization ID, item ID, item planning method, PO header and line IDs, rebuild flag, item confirm status, starting cumulative and authorized quantities in both primary and secondary UOMs, last receipt transaction ID, purchasing and primary UOMs, attribute category, and 15 descriptive attributes). It opens an explicit cursor on CHV_SCHEDULE_ITEMS restricted by ROWID with FOR UPDATE ... NOWAIT, then compares the fetched row values against the passed-in values as part of the Forms optimistic-locking contract.
  • delete_row1 — the procedure named in the user's search. Consistent with the surrounding ..._PKG_S1 naming pattern, this is the deletion handler used to remove a schedule item row from CHV_SCHEDULE_ITEMS, invoked from the form's delete-record trigger.
  • The remaining documented program units in the package (two additional entries among the four recorded) follow the standard Forms server-side pattern accompanying these handlers.

Tables Accessed

The only documented table referenced through APPS synonyms is CHV_SCHEDULE_ITEMS. lock_row reads it with a SELECT ... FOR UPDATE OF Schedule_Id NOWAIT to hold a row-level lock while validating that the on-screen record matches the database record. The delete handler removes the identified schedule item row from the same table. No other application tables are documented in the ETRM metadata for this package.

Usage Notes

This package body is tightly coupled to the Oracle Forms front end for supplier scheduling. The Lock_Row and delete_row1 routines are typically invoked from form-level triggers (for example, ON-LOCK and ON-DELETE / KEY-DELREC) to enforce optimistic locking and referential deletion semantics. When no row is found for the supplied X_Rowid, the code raises APP_EXCEPTION with the standard FND message FORM_RECORD_DELETED, which the form surfaces to the user. Because it is classified as OTHER rather than a public API, custom code should not call these routines directly against 12.1.1 or 12.2.2; integrations should instead use supported scheduling APIs. The metadata notes this package is referenced by one other package, indicating a narrow internal dependency chain in the scheduling module.