Search Results rlm_ship_delivery_pattern_sv




Overview

RLM_SHIP_DELIVERY_PATTERN_SV is a server-side PL/SQL package in the APPS schema that supports Oracle E-Business Suite's Transportation and Logistics / Release Management (RLM) functionality. Its primary business function is to resolve and apply ship delivery patterns — the rules that determine how demand lines are grouped, scheduled, and released for shipment based on customer ship-to terms, delivery calendars, and transportation constraints.

The package acts as a service layer within the RLM architecture. It reads interface staging data, correlates it against customer ship-to terms and shipping method definitions, and produces the delivery pattern information consumed by downstream demand-validation and component-scheduling packages. Its naming convention ("_SV" suffix) identifies it as a service/validation component that other RLM packages call rather than a user-facing form handler.

The object is validated (VALID status) in both 12.1.1 and 12.2.2, indicating the interface has remained stable across the two releases.

Key Procedures and Functions

The ETRM documentation records 23 procedures and functions in this package; procedure-level parameter lists are not published in the metadata, so they are described here by purpose only.

  • Delivery pattern resolution procedures — derive applicable shipping patterns from the combination of customer ship-to terms, customer item terms, and shipping method definitions.
  • Interface processing procedures — read staged records from RLM_INTERFACE_HEADERS and RLM_INTERFACE_LINES and match them to valid delivery rules.
  • Validation routines — confirm that a proposed ship-to/ship-method combination has a defined delivery pattern before downstream processing proceeds.
  • Lookup and query functions — retrieve delivery codes, ship method attributes, and customer ship-to terms for use by calling packages.

Because the API classification is "OTHER," these are internal service entry points rather than a formally published public API. They are intended to be called by sibling RLM packages, not by external integrations.

Tables Accessed

  • RLM_CUST_SHIPTO_TERMS / RLM_CUST_SHIPTO_TERMS_ALL — customer ship-to level terms that constrain which delivery patterns apply.
  • RLM_CUST_ITEM_TERMS_ALL — item-specific customer terms layered on top of ship-to terms.
  • RLM_SHIP_DELIVERY_CODES — the delivery code definitions used to classify shipments.
  • RLM_INTERFACE_HEADERS / RLM_INTERFACE_LINES — inbound staging tables for demand and shipment interface data.
  • ECE_TP_GROUP / ECE_TP_HEADERS — trading partner group and header information, used to link delivery patterns to trading partners.
  • HZ_CUST_ACCOUNTS / HZ_CUST_ACCT_SITES — Trading Community Architecture customer and site records for ship-to identification.
  • MTL_INTERORG_SHIP_METHODS — inter-org shipping method definitions that determine valid transport modes.
  • PLITBLM — the standard Oracle PL/SQL table-of-varchar2 type used for passing arrays of values internally.
  • RLM_CORE_SV and STANDARD — shared utility packages supplying common RLM and Oracle standard routines.

Usage Notes

RLM_SHIP_DELIVERY_PATTERN_SV is not invoked directly from an Oracle Forms screen or a standalone concurrent program. It is an internal dependency, referenced by RLM_COMP_SCH_TO_DEMAND_SV, RLM_MANAGE_DEMAND_SV, RLM_TPA_SV, and RLM_VALIDATEDEMAND_SV. These four callers drive demand validation, component scheduling, and trading-partner availability processing; whenever those programs execute, this package supplies the delivery-pattern logic.

Custom code extending RLM functionality should call the higher-level caller packages rather than this service package directly, since the "_SV" layer has no documented parameter contract and may change between patches. When troubleshooting demand validation failures or unexpected delivery scheduling in RLM, this package and the RLM_CUST_SHIPTO_TERMS / RLM_SHIP_DELIVERY_CODES configuration data are appropriate starting points for investigation.