Search Results rlm_ship_delivery_codes_all

Overview

The RLM_SHIP_DELIVERY_CODES view is a Release Management (RLM) dictionary object within Oracle E-Business Suite 12.1.1 and 12.2.2. It presents shipping calendar and delivery-rule definitions — the named rules that determine the percentage of an order or shipment quantity that should be released on each day of the week. In the RLM shipping model, a delivery code describes the picking, packing, and shipping schedule profile assigned to a customer, ship-to location, or carrier, and thus drives how shipping dates are spread across the working week.

The view is a dated, translated-representation view over the RLM_SHIP_DELIVERY_CODES_ALL table. Because it exposes a wide set of descriptive flexfield columns (both the standard ATTRIBUTE1–ATTRIBUTE15 set and a parallel TP_ATTRIBUTE1–TP_ATTRIBUTE15 set with TP_ATTRIBUTE_CATEGORY), it is frequently used in reporting, interfaces, and conversion programs that must read both core and additional attribute information on a delivery code.

Underlying Base Objects

The view text selects exclusively from RLM_SHIP_DELIVERY_CODES_ALL. No other base tables or joined objects are referenced in the documented view definition. The _ALL suffix indicates a multi-org (operating unit) table; the view applies a row-level security predicate against ORG_ID derived from the session's CLIENT_INFO context.

• RLM_SHIP_DELIVERY_CODES_ALL — the single documented source object, holding organization-specific delivery-code rows.
• RLM_SHIP_DELIVERY_CODES — the secured view that filters those rows to the current operating unit.

The multi-org filter decodes the first ten characters of USERENV('CLIENT_INFO'), substituting -99 when the value is blank or undefined, and compares it to NVL(ORG_ID, -99). This ensures that rows belonging only to the caller's organization (or rows with no organization, such as shared definitions) are returned.

Key Columns

• SHIP_DELIVERY_RULE_NAME — the user-facing name of the delivery rule or shipping code; the primary business identifier.
• DESCRIPTION — descriptive text for the rule.
• MONDAY_PERCENT … SUNDAY_PERCENT — the percentage of the shipment quantity to be released on each named weekday, defining the weekly shipping profile.
• USER_MAINTAINABLE_FLAG — indicates whether the delivery code may be maintained by users, typically distinguishing seeded system rules from custom ones.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15 — the standard descriptive flexfield context and segments.
• TP_ATTRIBUTE_CATEGORY, TP_ATTRIBUTE1–TP_ATTRIBUTE15 — a second flexfield structure carried on the same record; TP_ATTRIBUTE1 is the column most often targeted by "tp_attribute1" searches.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program auditing columns identifying the request that last touched the row.

Common Use Cases and Queries

Typical uses include retrieving the weekly shipping distribution for a named delivery code, listing all user-maintainable codes in an operating unit, and reporting on flexfield values such as TP_ATTRIBUTE1.

Retrieve the shipping profile for a specific rule:

• SELECT ship_delivery_rule_name, monday_percent, tuesday_percent, wednesday_percent, thursday_percent, friday_percent, saturday_percent, sunday_percent FROM rlm_ship_delivery_codes WHERE ship_delivery_rule_name = :rule_name;

List maintainable delivery codes with their flexfield attributes:

• SELECT ship_delivery_rule_name, description, tp_attribute_category, tp_attribute1 FROM rlm_ship_delivery_codes WHERE user_maintainable_flag = 'Y' ORDER BY ship_delivery_rule_name;

Identify stale definitions using the concurrent program audit columns:

• SELECT ship_delivery_rule_name, last_updated_by, last_update_date FROM rlm_ship_delivery_codes WHERE program_update_date < SYSDATE - 365;

Because the view enforces operating-unit security automatically, queries issued from EBS sessions return only rows valid for the current organization, removing the need to add explicit ORG_ID predicates in most reports.