Search Results delete_row
Overview
CHV_ITEM_ORDERS_PKG_S1 is a small, single-purpose PL/SQL package body owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the sourcing and supplier scheduling area of the application and is classified under the generic API category "OTHER" in the ETRM repository, indicating that it is a supporting utility package rather than a formal public interface. The package delivers one documented procedure, delete_row(), whose sole responsibility is the removal of a specific item scheduling record from the CHV_ITEM_ORDERS table. Because it is retained as a versioned, standalone body (the header shows an original revision dated 1999), it reflects the legacy structure of the supplier scheduling data model, where item-level scheduling lines are maintained independently of the parent schedule header.
Key Procedures and Functions
The package exposes one documented procedure:
- delete_row — Deletes a single row from the CHV_ITEM_ORDERS table, identified by the combination of a schedule identifier and a schedule item identifier. Both values are supplied by the caller as required inputs. The procedure issues a direct DELETE against the table and then performs a
SQL%NOTFOUNDcheck; when no matching row is located, the handler executes a NULL statement, meaning the absence of a row is tolerated silently rather than being raised as an error. This makes the routine effectively idempotent: calling it for a non-existent combination completes without exception. The procedure returns no value and raises no user-defined exception on the empty-result path.
Tables Accessed
The package references a single table through the APPS synonym layer:
- CHV_ITEM_ORDERS — This is the only documented table accessed, and the procedure performs a write (DELETE) against it. The deletion is scoped by
schedule_idandschedule_item_id, making it the item-level scheduling detail table used within the supplier scheduling module. The parent schedule header is not touched by this package; only the item order line is affected.
Usage Notes
Given its narrow scope and the absence of validation, commit handling, or error signaling, CHV_ITEM_ORDERS_PKG_S1 is typically invoked as a subordinate cleanup routine rather than as an end-user-facing action. In practice it is called from:
- Forms and OA Framework pages in the supplier scheduling area, when a user removes an item from a schedule and the underlying detail row must be purged.
- Concurrent programs or batch routines that reconcile or regenerate scheduling data, where orphaned or superseded item order rows are deleted before re-insertion.
- Custom code and other packages, consistent with the ETRM record showing it is referenced by one other package. Developers integrating with scheduling data should invoke this procedure rather than issuing ad-hoc DELETEs, to preserve consistency with the packaged logic.
Because the procedure does not commit, the calling transaction retains control of transaction boundaries. Additionally, it performs no dependency or referential checks; callers are responsible for ensuring that dependent child records do not exist prior to deletion, as the constraint enforcement (or lack thereof) resides entirely at the database level. The original header comment indicates the object has been stable since its initial porting revision, and no overloads or additional procedures are documented in the ETRM metadata for this package body.
-
APPS.GMI_TO_FORM_TROLIN SQL Statements
12.2.2
-
APPS.GMI_TO_FORM_TROLIN SQL Statements
12.1.1
-
APPS.OKC_NUMBER_SCHEME_PVT SQL Statements
12.1.1
-
APPS.OE_PORTAL_HEADER SQL Statements
12.2.2
-
APPS.OE_PORTAL_HEADER SQL Statements
12.1.1
-
APPS.OKL_XMP_PVT SQL Statements
12.1.1
-
APPS.CHV_AUTHORIZATIONS_PKG_S1 SQL Statements
12.1.1
-
APPS.OKC_NUMBER_SCHEME_PVT SQL Statements
12.2.2
-
APPS.OKL_XMP_PVT SQL Statements
12.2.2
-
APPS.CHV_HORIZ_SCHEDULES_PKG_S1 SQL Statements
12.1.1
-
APPS.CHV_HORIZ_SCHEDULES_PKG_S1 SQL Statements
12.2.2
-
APPS.XLA_AAD_LINE_DEFN_ASSGNS_F_PVT SQL Statements
12.1.1
-
APPS.CHV_AUTHORIZATIONS_PKG_S1 SQL Statements
12.2.2
-
APPS.XLA_AAD_LINE_DEFN_ASSGNS_F_PVT SQL Statements
12.2.2
-
APPS.OKC_NUMBER_SCHEME_DTL_PVT SQL Statements
12.1.1
-
APPS.CHV_ITEM_ORDERS_PKG_S1 SQL Statements
12.1.1
-
APPS.CHV_ITEM_ORDERS_PKG_S1 SQL Statements
12.2.2
-
APPS.GR_EIN_ASL_RISKS_PKG SQL Statements
12.2.2
-
APPS.OKS_SUBSCR_PTRNS_PUB SQL Statements
12.1.1
-
APPS.OKC_NUMBER_SCHEME_DTL_PVT SQL Statements
12.2.2
-
APPS.OKS_SUBSCR_HDR_PUB SQL Statements
12.1.1
-
APPS.OKS_SUBSCR_HDR_PUB SQL Statements
12.2.2
-
APPS.OKL_QUL_PVT SQL Statements
12.1.1
-
APPS.OKL_LAT_PVT SQL Statements
12.2.2
-
APPS.OKL_QUL_PVT SQL Statements
12.2.2
-
APPS.XLA_AAD_HEADER_AC_ASSGNS_F_PVT SQL Statements
12.2.2
-
APPS.OKL_LAT_PVT SQL Statements
12.1.1
-
APPS.GMD_EVENT_SPEC_DISP_PVT SQL Statements
12.2.2
-
APPS.GMD_EVENT_SPEC_DISP_PVT SQL Statements
12.1.1
-
APPS.OKS_SUBSCR_ELEMS_PUB SQL Statements
12.2.2
-
APPS.OKL_PSY_PVT SQL Statements
12.2.2
-
APPS.GMD_SPEC_RESULTS_PVT SQL Statements
12.2.2
-
APPS.GMD_COMPOSITE_SPEC_DISP_PVT SQL Statements
12.2.2
-
APPS.GR_SAFETY_CATEGORIES_B_PKG SQL Statements
12.1.1
-
APPS.GR_ITEM_GROUPS_B_PKG SQL Statements
12.1.1
-
APPS.GR_COVER_LETTERS_B_PKG SQL Statements
12.1.1
-
APPS.GR_EIN_ASL_RISKS_PKG SQL Statements
12.1.1
-
APPS.OKL_PSY_PVT SQL Statements
12.1.1
-
APPS.GR_COVER_LETTERS_B_PKG SQL Statements
12.2.2
-
APPS.GR_SAFETY_CATEGORIES_B_PKG SQL Statements
12.2.2
-
APPS.GMD_SAMPLE_SPEC_DISP_PVT SQL Statements
12.1.1
-
APPS.GMD_COMPOSITE_RESULT_ASSOC_PVT SQL Statements
12.2.2
-
APPS.GMD_SPEC_RESULTS_PVT SQL Statements
12.1.1
-
APPS.GMD_COMPOSITE_SPEC_DISP_PVT SQL Statements
12.1.1
-
PACKAGE BODY: APPS.CHV_ITEM_ORDERS_PKG_S1
12.2.2
-
PACKAGE BODY: APPS.CHV_AUTHORIZATIONS_PKG_S1
12.2.2
-
APPS.XLA_LINE_DEFN_AC_ASSGNS_F_PVT SQL Statements
12.1.1
-
APPS.XLA_ACCT_CLASS_ASSGNS_F_PKG SQL Statements
12.1.1
-
APPS.PO_REQUISITION_LINES_PKG1 SQL Statements
12.1.1
-
PACKAGE BODY: APPS.CHV_HORIZ_SCHEDULES_PKG_S1
12.1.1