Search Results update_line

Overview

POS_SUPPLIER_ITEM_TOL_PKG is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema that maintains supplier item tolerance data used in the procurement and receiving flow. Its central responsibility is managing the PO_SUPPLIER_ITEM_TOLERANCE table, which stores the number of days in advance and the tolerance percentage allowed for a given Approved Supplier List (ASL) entry. This tolerance data governs the quantity over-receipt or under-receipt permitted against a supplier item before an exception is raised, and controls the receiving-window rules applied to anticipated shipments. The package is classified as OTHER in the ETRM repository, meaning it is treated as a supporting internal API rather than a published integration interface. The header comment identifies it as a noship build originating in 2005, which confirms it is a stable, long-lived component of the Purchasing (POS) module family. It is referenced by one other package, indicating a narrow and well-defined dependency footprint.

Key Procedures and Functions

The package exposes three documented procedures. Each is a straightforward data manipulation routine with no return value; error handling is limited to re-raising the original exception via RAISE so that the calling form or program can present the underlying Oracle error.

• STORE_LINE — Inserts a new tolerance record into PO_SUPPLIER_ITEM_TOLERANCE for a specified ASL entry. It captures the days-in-advance value, the tolerance value, and audit columns. Unsupplied numeric inputs are defaulted to zero, and the USING_ORGANIZATION_ID column is populated with -1, denoting a global or unrestricted organization context.
• UPDATE_LINE — Modifies an existing tolerance record. This is the procedure associated with the user search term "update_line". It updates the number-of-days and tolerance values and refreshes the audit columns, while its WHERE clause matches on the ASL identifier together with the previous days-in-advance value. That prior-value predicate acts as the row discriminator, allowing the caller to target a specific tolerance row for an ASL that may hold more than one.
• DELETE — Removes all tolerance rows associated with a given ASL identifier, effectively clearing the supplier item's tolerance configuration.

Tables Accessed

The single documented table is PO_SUPPLIER_ITEM_TOLERANCE, referenced through an APPS synonym. The package writes to it in all three procedures: STORE_LINE performs an insert; UPDATE_LINE performs an update; and DELETE performs a delete. The key columns involved are ASL_ID, USING_ORGANIZATION_ID, NUMBER_OF_DAYS, and TOLERANCE, together with the standard WHO audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) plus CREATION_DATE and CREATED_BY. No reads of other application tables are documented, so the package is self-contained with respect to its data access.

Usage Notes

Because this package manipulates supplier item tolerance data by ASL identifier, it is typically invoked from the Oracle Purchasing setup and supplier-item maintenance forms, and potentially from receiving-options configuration screens where tolerance and lead-time tolerances are defined. In Oracle EBS 12.1.1 and 12.2.2, such packages are commonly called by form-level triggers or by form PL/SQL libraries rather than by concurrent programs, since the operations are record-scoped and user-driven. Custom code that needs to programmatically create, amend, or remove supplier item tolerance rules may call these procedures directly, but must honor the calling conventions: UPDATE_LINE requires the previous days-in-advance value so that the correct row is matched, and DELETE removes every row for the ASL rather than a single record. The procedures do not perform commit or rollback, leaving transaction control to the caller. Developers extending this functionality should avoid inventing parameter lists and instead confirm the signatures against the deployed specification before writing dependent code.