Results for “mtl_client_parameters_u2”

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

Overview

INV.MTL_CLIENT_PARAMETERS is a client-level configuration and parameter table within the Oracle E-Business Suite Inventory (INV) schema. It stores per-client operational settings that govern third-party logistics (3PL) processing, warehouse shipping execution, license plate number (LPN) generation, and outbound delivery behavior. Each row corresponds to a distinct client (trading partner) and acts as a single control point from which Oracle Warehouse Management (WSH) and related fulfillment processes derive default behavior. Because it holds descriptive attributes, flags, and thresholds tied to a business key rather than serving as an associative structure between two hubs, the metadata's heuristic Data Vault classification is satellite-leaning. In a Data Vault model this table is best treated as a satellite attached to a client hub, with CLIENT_ID and CLIENT_CODE functioning as the business keys and the parameter flags as descriptive, historically tracked attributes.

Key Information Stored

The table is defined with 40 documented columns in the 12.2.2 physical schema, owned by INV and stored in the APPS_TS_TX_DATA tablespace with 10 percent PCTFREE. The surrogate primary key is MTL_CLIENT_PARAMETERS_PK on CLIENT_ID, a NUMBER column that uniquely identifies each client. Two unique indexes serve as business-key candidates: MTL_CLIENT_PARAMETERS_U1 on CLIENT_ID and MTL_CLIENT_PARAMETERS_U2 on CLIENT_CODE (VARCHAR2(10)), the latter being the index referenced by the searched term. CLIENT_NUMBER (VARCHAR2(30)) provides an additional client reference, while TRADING_PARTNER_SITE_ID (NUMBER(15)) binds the client to a specific site.

Operational control columns include RECEIPT_ASN_EXISTS_CODE, which defines the action taken when a user selects a purchase order shipment despite an existing Advance Shipment Notice (ASN), and RMA_RECEIPT_ROUTING_ID, which sets the receipt routing for returns. Several auto-create delivery options are stored as flags: GROUP_BY_CUSTOMER_FLAG, GROUP_BY_FREIGHT_TERMS_FLAG, GROUP_BY_FOB_FLAG, GROUP_BY_SHIP_METHOD_FLAG, and AUTOCREATE_DEL_ORDERS_FLAG. Shipping and transportation parameters include SHIP_CONFIRM_RULE_ID, DELIVERY_REPORT_SET_ID, and OTM_ENABLED, indicating whether Oracle Transportation Management is active. LPN-related columns — LPN_PREFIX, LPN_SUFFIX, UCC_128_SUFFIX_FLAG, TOTAL_LPN_LENGTH, and LPN_STARTING_NUMBER — control license plate number formatting and generation. Standard WHO audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) and 15 descriptive ATTRIBUTE columns complete the structure.

Common Use Cases and Queries

Typical usage centers on retrieving configuration for a client before executing a warehouse or 3PL transaction. A common lookup resolves the internal client identifier from the client code:

• SELECT client_id, client_number FROM inv.mtl_client_parameters WHERE client_code = :p_client_code;
• SELECT client_code, otm_enabled, ship_confirm_rule_id FROM inv.mtl_client_parameters WHERE otm_enabled = 'Y';
• SELECT client_id, lpn_prefix, lpn_suffix, total_lpn_length FROM inv.mtl_client_parameters WHERE ucc_128_suffix_flag = 'Y';

Reporting scenarios include auditing which clients have enabled OTM, validating LPN formatting rules, and confirming ship confirm rule assignments against WSH_SHIP_CONFIRM_RULES. Administrators also query the table to verify auto-create delivery grouping flags before Pick Releasing, since AUTOCREATE_DEL_ORDERS_FLAG determines whether a delivery may contain lines from multiple orders. Because the table is narrow and keyed, it is frequently joined into order-to-shipment reconciliations and 3PL billing extracts.

Related Objects

MTL_CLIENT_PARAMETERS sits at the center of several warehouse and 3PL relationships. Foreign keys from this table reference HZ_CUST_ACCOUNTS via CLIENT_ID, HZ_PARTY_SITES via TRADING_PARTNER_SITE_ID, WSH_SHIP_CONFIRM_RULES via SHIP_CONFIRM_RULE_ID, and WSH_REPORT_SETS via DELIVERY_REPORT_SET_ID. Numerous downstream tables reference it: MTL_3PL_LOCATOR_OCCUPANCY and MTL_BILLING_RULE_LINES via CLIENT_CODE, and IEO_CAMPAIGNS_ALL, WSH_PICKING_RULES, WSH_NEW_DELIVERIES, WSH_DELIVERY_DETAILS, CCT_AGENT_RT_STATS, WSH_PICKING_BATCHES, and HR_H2PI_DATA_FEED_HIST via CLIENT_ID. These dependencies confirm the table's role as a foundational client master for shipping execution, picking, billing, and transportation reporting.