Search Results ship_delivery_rule_name_pk

Overview

RLM_SHIP_DELIVERY_CODES is a Release Management (RLM) table in the Oracle E-Business Suite that stores shipment and delivery pattern rules. It serves as the master repository of named delivery-calendar definitions used by Release Management to distribute a release quantity across the days of a week. Each row represents one ship/delivery pattern, identified by a user-defined rule name, and carries a percentage allocation for each weekday (Monday through Sunday). These patterns drive how scheduled shipment or delivery quantities are spread over time during release scheduling and pick-release processing.

The table resides in the RLM schema and is valid in both Oracle EBS 12.1.1 and 12.2.2. In 12.2.2 the documented physical schema contains 51 columns. The primary key is SHIP_DELIVERY_RULE_NAME_PK, defined on the single column SHIP_DELIVERY_RULE_NAME. Under the heuristic Data Vault classification mined from the foreign-key structure, this object is modeled as a standalone table. From a Data Vault perspective, it is best treated as a reference or hub-like entity keyed by the business rule name, without dependent link or satellite relationships documented in the ETRM metadata. The absence of documented foreign keys indicates that the table functions as a self-contained reference set consumed by other RLM components rather than as a transactional fact or junction.

Key Information Stored

The most significant columns fall into three functional groups: identity, pattern definition, and audit/descriptive attributes.

• SHIP_DELIVERY_RULE_NAME — the business identifier and primary key column (SHIP_DELIVERY_RULE_NAME_PK). It is the unique, user-recognizable name of the delivery pattern and the natural business-key candidate for lookups and joins.
• DESCRIPTION — free-text description of the rule's purpose or applicability.
• MONDAY_PERCENT, TUESDAY_PERCENT, WEDNESDAY_PERCENT, THURSDAY_PERCENT, FRIDAY_PERCENT, SATURDAY_PERCENT, SUNDAY_PERCENT — the seven weekday allocation percentages that define the pattern. Together these express how much of the release quantity ships or delivers on each day.
• USER_MAINTAINABLE_FLAG — indicates whether the rule is user-editable or system-supplied and protected from modification.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard Oracle EBS audit columns recording who created and last modified the row and when.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context, identifying the process that last touched the record.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle EBS descriptive flexfield (DFF) segment columns for extensibility.
• TP_ATTRIBUTE_CATEGORY, TP_ATTRIBUTE1 through TP_ATTRIBUTE15 — a second, trade-partner-oriented flexfield context used by RLM for additional pattern metadata.

Common Use Cases and Queries

Typical use cases include validating that a rule name exists before assigning it to a release, auditing which patterns are user-maintainable versus seeded, and reporting the weekly distribution profile of a pattern. The weekday percentages are commonly inspected to verify that allocations sum to 100 percent before a rule is used in scheduling.

• Retrieve a full pattern definition: SELECT SHIP_DELIVERY_RULE_NAME, DESCRIPTION, MONDAY_PERCENT, TUESDAY_PERCENT, WEDNESDAY_PERCENT, THURSDAY_PERCENT, FRIDAY_PERCENT, SATURDAY_PERCENT, SUNDAY_PERCENT FROM RLM.RLM_SHIP_DELIVERY_CODES WHERE SHIP_DELIVERY_RULE_NAME = :rule_name;
• List seeded versus user-defined rules: SELECT SHIP_DELIVERY_RULE_NAME, USER_MAINTAINABLE_FLAG FROM RLM.RLM_SHIP_DELIVERY_CODES ORDER BY USER_MAINTAINABLE_FLAG, SHIP_DELIVERY_RULE_NAME;
• Validate percentage totals: sum the seven weekday columns and flag rows that do not equal 100 for review.
• Flexfield-based reporting: query ATTRIBUTE_CATEGORY and ATTRIBUTE1..15, or the TP_ATTRIBUTE columns, to surface organization-specific extensions.

Related Objects

The ETRM metadata classifies this object as standalone, meaning no foreign keys are documented from RLM_SHIP_DELIVERY_CODES to other tables. The most significant referencing relationships are therefore logical rather than enforced, anchored on the SHIP_DELIVERY_RULE_NAME business key. Key objects to review alongside this table include:

• RLM_SHIP_DELIVERY_RULES or equivalent RLM allocation/pattern detail tables — any RLM object that stores shipment allocations keyed by the same rule name.
• Release Management scheduling and pick-release setup tables — objects that reference a delivery rule when a release is planned or generated.
• RLM lookup and reference views — presentation-layer views that expose SHIP_DELIVERY_RULE_NAME and DESCRIPTION for LOV and validation purposes.
• FND concurrent program tables (FND_CONCURRENT_REQUESTS, FND_PROGRAM) — resolvable through REQUEST_ID and PROGRAM_ID for audit reporting.
• RLM setup APIs and concurrent programs — interfaces used to create, copy, and validate delivery patterns during implementation.

Because referential integrity is not documented, join logic depends on the SHIP_DELIVERY_RULE_NAME column, and consumers should validate rule existence and percentage completeness at the application layer.