Results for “rlm_shipto_item_terms_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

RLM_SHIPTO_ITEM_TERMS_V is an APPS-owned database view in the Release Management (RLM) product family of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. It consolidates ship-to level customer item terms into a single denormalized reporting structure, joining customer account, address, customer item, commodity, and terms data. The view is designed to expose the negotiated sourcing and delivery agreements that govern how a specific customer item is shipped to a specific ship-to address from a specific ship-from organization.

The view is primarily consumed by ETRM (Enterprise Territory and Release Management) reporting, integration, and reconciliation logic. Because it surfaces customer, location, item, and terms attributes together, it removes the need for reporting tools and custom interfaces to reconstruct the same multi-table join. It is especially relevant to searches for CUST_ITEM_STATUS_CODE, since the view exposes that column directly alongside identifying and descriptive context.

Underlying Base Objects

The documented base objects include the following:

• HZ_CUST_ACCOUNTS — customer account header, supplying CUSTOMER_NAME and CUSTOMER_NUMBER.
• HZ_CUST_ACCT_SITES_ALL — customer account site information.
• HZ_LOCATIONS — ship-to address details such as CITY, POSTAL_CODE, PROVINCE, COUNTY, and the concatenated ADDRESS.
• HZ_PARTIES and HZ_PARTY_SITES — party and party-site resolution for address linkage.
• MTL_CUSTOMER_ITEMS — customer item number and description.
• MTL_CUSTOMER_ITEM_XREFS — cross-references between customer items and internal inventory items.
• MTL_COMMODITY_CODES — commodity classification for the item.
• MTL_ITEM_FLEXFIELDS — descriptive flexfield attributes for the item.
• RLM_CUST_ITEM_TERMS — the central terms table that drives CUST_ITEM_STATUS_CODE, ship-from organization, price list, tolerances, and planning/shipping day offsets.

RLM_CUST_ITEM_TERMS is the driving table for the terms-related columns, with the remaining objects providing descriptive enrichment via address, item, and commodity lookups.

Key Columns

The critical columns exposed by the view fall into several groups:

• Customer identification: CUSTOMER_ID, CUSTOMER_NAME, CUSTOMER_NUMBER, CUST_ITEM_TERMS_ID, CUSTOMER_ITEM_ID.
• Location: ADDRESS_ID, ECE_LOCATION_CODE, ADDRESS, CITY, POSTAL_CODE, PROVINCE, COUNTY.
• Item: CUSTOMER_ITEM_NUMBER, CUSTOMER_ITEM_DESC, COMMODITY_CODE.
• Terms and agreement: CUST_ITEM_STATUS_CODE, AGREEMENT_NAME, FUTURE_AGREEMENT_NAME, SHIP_FROM_ORG_ID, SHIP_DELIVERY_RULE_NAME, SHIP_METHOD, INTRANSIT_TIME, TIME_UOM_CODE.
• Planning and shipping offsets: PLN_FIRM_DAY_TO/FROM, PLN_FORECAST_DAY_TO/FROM, PLN_FROZEN_DAY_TO/FROM, and the corresponding SEQ_* and SHP_* day offset columns.
• Pricing and packaging: PRICE_LIST_ID, STD_PACK_QTY, ROUND_TO_STD_PACK_FLAG, DEMAND_TOLERANCE_ABOVE/BELOW.
• Audit attributes: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, ATTRIBUTE_CATEGORY, and ATTRIBUTE1 through ATTRIBUTE15.

CUST_ITEM_STATUS_CODE is the focal column for many queries because it indicates the active/inactive or lifecycle status of the customer item terms record as defined in RLM_CUST_ITEM_TERMS.

Common Use Cases and Queries

Typical uses include validating effective ship-to item terms, troubleshooting why a release or shipment used a particular delivery rule, and reconciling customer agreements against internal item masters. A representative query filtering on the searched column is:

• SELECT CUSTOMER_NAME, CUSTOMER_ITEM_NUMBER, ADDRESS_ID, SHIP_FROM_ORG_ID, CUST_ITEM_STATUS_CODE, SHIP_DELIVERY_RULE_NAME FROM RLM_SHIPTO_ITEM_TERMS_V WHERE CUST_ITEM_STATUS_CODE = 'ACTIVE';

Other common patterns join the view to shipment or order tables by CUSTOMER_ITEM_ID or SHIP_FROM_ORG_ID, or aggregate terms by CUSTOMER_ID to review agreement coverage. Because the view is read-only and denormalized, it is well suited to BI Publisher reports, Oracle Discoverer workbooks, and custom PL/SQL extraction programs within RLM.