Results for “round_to_std_pack_flag”

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

Overview

RLM_CUST_ITEM_TERMS_V is an APPS-owned reporting view in the Oracle E-Business Suite Release Management (RLM) module. It presents customer item terms — the contractual and planning rules that govern how a specific customer item is ordered, shipped, priced, and planned between a ship-from organization and a customer. The view consolidates customer master data, customer item definitions, commodity classifications, and the operational terms record into a single denormalized row per customer item terms entry.

Because customer item terms drive demand tolerances, cumulative quantity calculations, packaging rules, transit times, and planning horizon day offsets, this view serves as a convenient integration and reporting surface for order management, shipping, and planning processes. Rather than joining the customer, item, and terms tables separately, report writers and interface developers can query this view to retrieve fully resolved descriptive attributes (customer name, customer number, customer item number, commodity code) alongside the technical terms columns. The view is listed as VALID in the ETRM metadata for both 12.1.1 and 12.2.2.

Underlying Base Objects

The documented base objects underlying this view are:

• HZ_CUST_ACCOUNTS (SYNONYM) — supplies the customer account identity used for customer_id and related linkage.
• HZ_PARTIES (SYNONYM) — supplies the party-level attributes that resolve to customer name through the account relationship.
• MTL_COMMODITY_CODES (SYNONYM) — supplies commodity_code.
• MTL_CUSTOMER_ITEMS (SYNONYM) — supplies customer_item_number and customer_item_desc.
• MTL_CUSTOMER_ITEM_XREFS (SYNONYM) — supplies the cross-reference between the customer item and the internal inventory item.
• MTL_ITEM_FLEXFIELDS (VIEW) — provides item flexfield descriptive segments associated with the internal item.
• RLM_CUST_ITEM_TERMS (SYNONYM) — the primary terms table that supplies the bulk of the columns exposed by the view, aliased as TERMS in the view text.

The view therefore acts as a join hub: TERMS supplies the transactional terms record, while HZ and MTL objects enrich it with customer and item descriptive context.

Key Columns

The most significant columns fall into four groups. Identification columns include cust_item_terms_id, customer_item_id, customer_id, address_id, header_id, and ship_from_org_id. Descriptive columns include customer_name, customer_number, customer_item_number, customer_item_desc, and commodity_code. Calculation and planning columns include calc_cum_flag — the cumulative quantity calculation indicator matching the user's search term — along with cum_current_start_date, cum_previous_start_date, demand_tolerance_above, demand_tolerance_below, and the planning day offset pairs (pln_firm_day_from/to, pln_forecast_day_from/to, pln_frozen_day_from/to, seq_* and shp_* equivalents). Fulfillment and pricing columns include std_pack_qty, round_to_std_pack_flag, ship_method, ship_delivery_rule_name, intransit_time, time_uom_code, price_list_id, freight_code, use_edi_sdp_code_flag, and default_ship_from. Audit columns (creation_date, created_by, last_update_date, last_updated_by, request_id, program_id) and the attribute1–15 and tp_attribute1–4 descriptive flexfield columns complete the structure.

Common Use Cases and Queries

Typical uses include validating cumulative calculation setup, tracing planning horizons for a ship-from organization, and exporting customer item terms for external planning systems. For example, to locate terms where cumulative calculation is enabled for a given customer item:

• SELECT customer_number, customer_item_number, cust_item_terms_id, calc_cum_flag, cum_current_start_date FROM rlm_cust_item_terms_v WHERE calc_cum_flag = 'Y';
• SELECT customer_name, customer_item_number, ship_from_org_id, pln_firm_day_from, pln_firm_day_to, demand_tolerance_above, demand_tolerance_below FROM rlm_cust_item_terms_v WHERE ship_from_org_id = :org_id;
• SELECT cust_item_terms_id, agreement_name, future_agreement_name, std_pack_qty, round_to_std_pack_flag FROM rlm_cust_item_terms_v WHERE customer_id = :customer_id;

Because the view is read-only and denormalized, it is well suited to ad hoc queries and downstream extracts, while updates must always be directed to the RLM_CUST_ITEM_TERMS base table.