Results for “otm_enabled”

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

Overview

MTL_CLIENT_PARAMETERS is an Inventory (INV) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores configuration attributes for third-party logistics (3PL) clients and trading partners. It defines per-client defaults that govern fulfillment behavior, including shipping confirmation, delivery order creation, delivery report generation, and license plate number (LPN) generation. The table resides in the INV schema and is classified as VALID. Functionally, it acts as the master reference for client-level operational parameters used by Warehouse Management (WSH) and third-party logistics flows.

The ETRM metadata describes this object as a "Client Parameters table." Under the heuristic Data Vault classification derived from its foreign key structure, MTL_CLIENT_PARAMETERS is satellite-leaning — it carries descriptive attributes that extend a hub (the client itself, referenced via CLIENT_ID to HZ_CUST_ACCOUNTS), while also anchoring several downstream fact-like references. This is a modeling suggestion rather than a mandated design.

Key Information Stored

The table comprises 40 documented columns. The most operationally significant are:

• CLIENT_ID — surrogate primary key (MTL_CLIENT_PARAMETERS_PK) and foreign key to HZ_CUST_ACCOUNTS; identifies the client account.
• CLIENT_CODE — unique business key (MTL_CLIENT_PARAMETERS_U2); the externally recognizable client identifier.
• CLIENT_NUMBER — alternate client reference used in 3PL integration.
• TRADING_PARTNER_SITE_ID — foreign key to HZ_PARTY_SITES; ties the client to a specific party site.
• SHIP_CONFIRM_RULE_ID — foreign key to WSH_SHIP_CONFIRM_RULES; mandates the ship confirmation rule applied to the client's deliveries.
• DELIVERY_REPORT_SET_ID — foreign key to WSH_REPORT_SETS; selects the report set used for delivery documentation.
• AUTOCREATE_DEL_ORDERS_FLAG — controls whether delivery orders are auto-generated.
• RECEIPT_ASN_EXISTS_CODE — governs advance shipping notice behavior on receipts.
• RMA_RECEIPT_ROUTING_ID — routing reference for return material authorizations.
• OTM_ENABLED — indicates Oracle Transportation Management integration.
• GROUP_BY_*_FLAG columns (CUSTOMER, FREIGHT_TERMS, FOB, SHIP_METHOD) — control grouping logic during picking and delivery.
• LPN_PREFIX, LPN_SUFFIX, TOTAL_LPN_LENGTH, LPN_STARTING_NUMBER, UCC_128_SUFFIX_FLAG — parameterize license plate number generation, including UCC-128 compliance.
• ATTRIBUTE1–ATTRIBUTE15 — the standard EBS descriptive flexfield (DFF) attribute columns.

Two unique indexes serve as business-key candidates: MTL_CLIENT_PARAMETERS_U1 (CLIENT_ID) and MTL_CLIENT_PARAMETERS_U2 (CLIENT_CODE), alongside the documented UK1 on CLIENT_CODE.

Common Use Cases and Queries

The table is queried whenever 3PL client defaults must be resolved, such as during picking, packing, ship confirmation, and delivery report generation. A typical lookup resolves the ship confirmation rule for a client:

• SELECT mcp.client_code, mcp.ship_confirm_rule_id FROM mtl_client_parameters mcp WHERE mcp.client_code = :client_code;

Reporting scenarios commonly join this table to WSH_SHIP_CONFIRM_RULES to validate rule assignments, or to WSH_REPORT_SETS to confirm delivery documentation. A left outer join pattern is useful to detect clients lacking configured rules:

• SELECT mcp.client_code, scr.rule_name FROM mtl_client_parameters mcp LEFT JOIN wsh_ship_confirm_rules scr ON mcp.ship_confirm_rule_id = scr.rule_id;

Inventory reconciliations frequently join to dependent tables such as WSH_DELIVERY_DETAILS via CLIENT_ID, and to MTL_BILLING_RULE_LINES via CLIENT_CODE to associate billing rules with clients. Data-quality reports are used to find records missing TRADING_PARTNER_SITE_ID or with incomplete LPN configuration.

Related Objects

MTL_CLIENT_PARAMETERS sits at the center of several FK relationships. The most significant are:

• HZ_CUST_ACCOUNTS — joined on MTL_CLIENT_PARAMETERS.CLIENT_ID, providing the client master record.
• HZ_PARTY_SITES — joined on TRADING_PARTNER_SITE_ID, defining the trading partner location.
• WSH_SHIP_CONFIRM_RULES — joined on SHIP_CONFIRM_RULE_ID, supplying the shipping confirmation rule definition.
• WSH_REPORT_SETS — joined on DELIVERY_REPORT_SET_ID, sourcing delivery report configuration.
• WSH_DELIVERY_DETAILS and WSH_NEW_DELIVERIES — reference this table via CLIENT_ID, linking deliveries to client defaults.
• WSH_PICKING_RULES and WSH_PICKING_BATCHES — reference CLIENT_ID for pick planning.
• MTL_BILLING_RULE_LINES and MTL_3PL_LOCATOR_OCCUPANCY — reference CLIENT_CODE, tying billing rules and locator occupancy to the client.
• IEO_CAMPAIGNS_ALL and CCT_AGENT_RT_STATS — also join on CLIENT_ID for campaign and agent statistics.

These relationships confirm the table's role as a hub of client-level configuration in 3PL and warehouse fulfillment flows within INV and WSH.