Search Results wsh_tp_release




Overview

WSH_TP_RELEASE is a PL/SQL package owned by the APPS schema within Oracle E-Business Suite, supporting both release 12.1.1 and 12.2.2. It belongs to the Oracle Transportation/Warehouse Shipping execution product family and encapsulates Trading Partner (TP) specific logic. The package is classified under the generic API category OTHER in the ETRM metadata rather than as a public or private interface, which indicates that its procedures are primarily intended for internal consumption by Oracle Shipping and Transportation modules rather than for direct third-party integration.

The principal business function of the package is to manage the planning state of shipping and transportation entities, specifically deliveries, delivery details, and trips. It governs firming and unfirming actions, controls whether entities are considered for planning through the ignore-for-planning flag, and computes transportation-related dates such as promise dates, schedule arrival and ship dates, and acceptable date ranges. The package also enforces consistency rules across shipments, ensuring that status changes propagate correctly through the trip, delivery, and carrier manifest hierarchy.

Key Procedures and Functions

The package exposes eight documented procedures. Each is described below by purpose only; the metadata does not expose reliable parameter lists for all of them, and no parameter detail is invented here.

  • CHANGE_IGNOREPLAN_STATUS — Changes the ignore-for-planning status of a specified entity, supporting either an exclusion (IGNORE_PLAN) or inclusion (INCLUDE_PLAN) action. The package comments stipulate that all delivery details of a delivery must assume the same ignore status as the delivery, and that trips with a conflicting ignore status require manual unassignment. The comments further note that transportation planning workbench records, carrier manifest lines, and deliveries must always be marked with the ignore-for-planning flag.
  • FIRM_ENTITY — Firms a specified entity, locking it from further planning modification. Unfirming a trip also unfirms its carrier manifest where the carrier manifest is firm.
  • UNFIRM_ENTITY — Reverses a firming action and accepts a plan or unplan action designation to return the entity to a planning-eligible state.
  • CALCULATE_TP_DATES — Computes transportation planning dates for an entity, working with request date types and a range of scheduling and promise date inputs including latest acceptable date, promise date, schedule arrival date, schedule ship date, earliest acceptable date, and demand satisfaction date.
  • CALCULATE_CONT_DEL_TPDATES — Performs an analogous date calculation for container and delivery combinations.
  • LOG_TPDATE_EXCEPTION — Records exceptions encountered during transportation date calculation, supporting diagnostic and error-handling flows.
  • CHECK_SHIPSET_IGNOREFLAG — Validates the ignore-for-planning flag consistency across a ship set, supporting the propagation rules described in the package header comments.

Tables Accessed

Through APPS synonyms, the package reads and writes several shipping and order management tables.

  • WSH_NEW_DELIVERIES and WSH_DELIVERY_DETAILS — Core delivery and delivery detail records whose ignore-for-planning and firming status are manipulated.
  • WSH_DELIVERY_LEGS — Delivery leg data used in date and routing calculations.
  • WSH_TRIPS and WSH_TRIP_STOPS — Trip headers and their stops, central to firming, unfirming, and trip-level ignore status propagation.
  • MTL_SYSTEM_ITEMS — Item master attributes referenced for the items being shipped.
  • OE_ORDER_LINES_ALL — Sales order line data used to derive demand and scheduling dates.
  • PLITBLM — The standard Oracle EBS PL/SQL table storage used to carry identifier collections passed into the API.

Usage Notes

WSH_TP_RELEASE is invoked indirectly through Oracle Shipping and Transportation execution flows, including Shipping Transactions and Transportation Planning workbench functionality, where users firm or unfirm deliveries and trips or toggle ignore-for-planning flags. It is also referenced by twenty other packages, confirming that it operates as a shared internal utility layer rather than an entry-point API. The documented tables are accessed via APPS synonyms, and the $Header comment records a 2007 revision, consistent with long-standing core shipping code carried forward into 12.1.1 and 12.2.2. Because the package is classified as OTHER and its procedures are not published as formal open interfaces, custom code should treat it as internal and prefer supported public shipping APIs for integrations.