Search Results reschedule_ship_set




Overview
Explore in AI Chat

Overview

The APPS.OE_RSCH_SETS_CONC_REQUESTS package is an Order Management utility in Oracle E-Business Suite that supports the rescheduling of ship sets. A ship set is a grouping of order lines that must ship together, governed by the set definition held in the OE_SETS table. The package provides a single, concurrent-program-oriented entry point, RESCHEDULE_SHIP_SET, which applies date-shift logic to the scheduling of lines belonging to identified ship sets.

The package is declared with AUTHID CURRENT_USER, meaning its SQL executes under the privileges of the invoking schema rather than the definer. The header comment ($Header: OEXCRSHS.pls 120.0) indicates the source file was last revised in 2005 and shipped with the application, classifying the object as standard Oracle-delivered code rather than a customer extension. In ETRM the API classification is recorded as OTHER, reflecting that this is not a public, supported interfacing API but an internal concurrent-request driver.

The user search term reschedule_ship_set maps directly to the package's sole documented procedure, confirming that this object is the relevant target for that functionality.

Key Procedures and Functions

One procedure is documented:

  • RESCHEDULE_SHIP_SET — The package's central routine. It accepts a set of selection and offset criteria and performs the rescheduling of ship sets that fall within the requested range. Consistent with Oracle concurrent program conventions, it returns the standard ERRBUF and RETCODE out parameters used for message reporting and request completion status. Its input parameters define the range of orders to process (order number low and high bounds), the scheduling window expressed as start-from and end-from day offsets, and an explicit ship set identifier (p_set_id) to narrow processing to a specific set.

No functions or additional procedures are documented. The parameter list should be treated as internal to the concurrent driver; custom code should not rely on calling it directly with undocumented assumptions.

Tables Accessed

The package operates against the following tables through APPS synonyms:

  • OE_ORDER_HEADERS — Read to identify and filter orders by the order number range supplied to the procedure, and to derive order-level scheduling context.
  • OE_ORDER_LINES and OE_ORDER_LINES_ALL — The primary targets for the rescheduling operation. OE_ORDER_LINES_ALL holds the base line records including schedule and ship date attributes; OE_ORDER_LINES exposes the line data used during processing. The date-offset logic is applied to lines associated with the identified ship sets.
  • OE_SETS — Stores the ship set definitions. It is used to resolve which lines belong to a given set, particularly when limiting processing by p_set_id.
  • PLITBLM — An Oracle Applications internal index-by table type (a PL/SQL table of VARCHAR2) used for in-memory collection handling within the procedure, rather than as a data-bearing application table.

Usage Notes

Given its ERRBUF/RETCODE signature and name ending in _CONC_REQUESTS, this package is designed to be invoked as a concurrent program from the Order Management responsibility, most likely through a report or request submission form that registers RESCHEDULE_SHIP_SET as the executable. Parameters such as order number ranges, day offsets, and set ID are populated from the concurrent program's parameter form.

Because the package is classified as OTHER and is not a documented public API, it should not be called directly from custom PL/SQL as a supported interface. The supported path for scheduling changes is the standard Order Management user interface and the Order Management public APIs. Direct invocation carries risk of bypassing validation, profile-dependent behavior, or processing dependencies that the concurrent manager handles at runtime. The package is referenced by no other documented packages, reinforcing its role as a terminal, standalone driver rather than a shared library. In EBS 12.1.1 and 12.2.2 the object is delivered as-is, with the 12.2 online patching architecture preserving the same package body behavior.