Search Results get_tolerance

Overview

OE_SHIPPING_INTEGRATION_PUB is a public PL/SQL API in the Oracle E-Business Suite Order Management (OE) module, owned by the APPS schema and declared with AUTHID CURRENT_USER. It provides the interface layer that bridges Order Management order lines with Oracle Shipping execution. In the 12.1.1 and 12.2.2 releases this package is central to the fulfillment lifecycle, where an order line progresses through workflow toward the SHIP_LINE activity and must be validated, credited, checked for holds, toleranced, and finally signaled to the Shipping module for delivery creation.

The package supports both the traditional order line shipping flow and ATO (Assemble-to-Order) configured line shipping, exposing functions that interrogate the workflow state of a line and procedures that drive or evaluate the shipping interface. Because the API classification is PUB, it is intended for supported external invocation—by forms, concurrent programs, Shipping Execution, or customer extensions—rather than being an internal-only helper.

Key Procedures and Functions

• IS_ACTIVITY_SHIPPING — A boolean-returning function that determines whether the current workflow activity for a given line is SHIP_LINE. It returns FND_API.G_TRUE when the line is at the SHIP_LINE activity and FND_API.G_FALSE otherwise, allowing callers to gate shipping actions on workflow position.
• COMPLETE_SHIP_LINE_ACTIVITY — Completes the SHIP_LINE workflow activity for a line, with a prerequisite that the line already resides at that activity. It confirms the SHIP_LINE state before advancing the workflow.
• UPDATE_SHIPPING_INTERFACE — Updates the shipping interface records, propagating order line data into the structures Shipping reads when it processes deliveries.
• GET_SET_SMC_INTERFACE_STATUS — Returns interface status for the SetSMC (ship set / model configuration) processing, using the Setsmc input and output record types documented for bug 3623149.
• CREDIT_CHECK — Evaluates credit standing for the line before shipping is allowed to proceed.
• CHECK_HOLDS_FOR_SC — Checks for holds applicable to the shipping/SC context, preventing release of held lines.
• GET_TOLERANCE — Retrieves tolerance information, supporting over- and under-shipment validation.
• GET_MIN_MAX_TOLERANCE_QUANTITY — Derives minimum and maximum allowable ship quantities from tolerance rules.
• GET_QUANTITY — Returns the quantity associated with the line for shipping calculations.
• CHECK_IMPORT_PENDING_LINES — Detects lines still pending import, guarding against shipping incomplete orders.
• ATO_CONFIG_LINE_SHIP_NOTIFIED — Signals or records shipping notification for ATO configuration lines.

Tables Accessed

• OE_ORDER_LINES / OE_ORDER_LINES_ALL — The primary order line records supplying line_id, quantity, and workflow context.
• WSH_DELIVERY_DETAILS — Shipping delivery detail records created or updated as lines are transferred to Shipping.
• MTL_SYSTEM_ITEMS — Item master attributes (shippable, ATO flags) used during validation.
• WF_ITEM_ACTIVITY_STATUSES / WF_PROCESS_ACTIVITIES — Workflow engine tables consulted to determine whether the current activity is SHIP_LINE.
• PLITBLM — PL/SQL internal table structure used for line collections and bulk processing.

Usage Notes

This package is typically invoked from the Order Management forms and from the fulfillment workflow when a line reaches the SHIP_LINE activity, from Shipping Execution when processing delivery details, and from concurrent programs that manage pending lines and interface updates. Five other packages reference it, indicating downstream dependencies. Custom code extending the shipping flow should call IS_ACTIVITY_SHIPPING before COMPLETE_SHIP_LINE_ACTIVITY to respect workflow prerequisites, and should expect FND_API-style return statuses. Because versions differ between 12.1.1 and 12.2.2 in the surrounding shipping architecture, integrators should validate procedure signatures against the target instance's ETRM record.