Search Results ship_confirm_document_set_name

Overview

The view APPS.MTL_CLIENT_PARAMETERS_V is a reporting and integration layer over the Oracle E-Business Suite client-level configuration used by the Warehouse Management and shipping execution modules. It presents decoded and denormalized client parameters, joining the underlying parameter table to descriptive values held in related setup tables so that downstream reports, interfaces, and shipping logic can resolve identifiers such as rule names, routing names, and document set names without additional lookups. Within Oracle EBS 12.1.1 and 12.2.2, the view is owned by the APPS schema and is primarily consumed by Shipping Execution, Trading Partner, and Logistics-related processes, including those interfacing with Oracle Transportation Management when the OTM_ENABLED flag is set.

The view is particularly relevant to the search term ship_conf_rule, since it exposes both SHIP_CONFIRM_RULE_ID and the resolved SHIP_CONFIRM_RULE_NAME derived from WSH_SHIP_CONFIRM_RULES. This allows ship confirmation behavior configured per client to be reported and validated in a readable form.

Underlying Base Objects

The view is defined over the following documented base objects:

• MTL_CLIENT_PARAMETERS (synonym) — the primary table holding client parameter rows, providing most columns including the ship confirm rule identifier, LPN attributes, grouping flags, and descriptive flexfield attributes.
• HZ_PARTIES (synonym) — supplies the client name (PARTY_NAME) associated with the customer.
• HZ_CUST_ACCOUNTS (synonym) — referenced for the customer account context that links parties to client parameters.
• RCV_ROUTING_HEADERS (view) — provides ROUTING_NAME for the receipt routing referenced by RMA_RECEIPT_ROUTING_ID.
• WSH_SHIP_CONFIRM_RULES (synonym) — provides NAME as SHIP_CONFIRM_RULE_NAME for the ship confirm rule identified by SHIP_CONFIRM_RULE_ID.
• WSH_REPORT_SETS (synonym) — provides NAME as SHIP_CONFIRM_DOCUMENT_SET_NAME for the delivery report set identified by DELIVERY_REPORT_SET_ID.

The view is structured as an inline subquery that joins MTL_CLIENT_PARAMETERS to these lookup objects and then projects the resulting columns with ROWID retained as ROW_ID.

Key Columns

• CLIENT_ID, CLIENT_CODE, CLIENT_NUMBER — identifiers for the client/trading partner.
• CLIENT_NAME — resolved party name from HZ_PARTIES.
• SHIP_CONFIRM_RULE_ID / SHIP_CONFIRM_RULE_NAME — the ship confirmation rule and its descriptive name from WSH_SHIP_CONFIRM_RULES.
• ROUTING_NAME — name of the receipt routing from RCV_ROUTING_HEADERS.
• SHIP_CONFIRM_DOCUMENT_SET_NAME — report set name from WSH_REPORT_SETS.
• OTM_ENABLED — indicates Oracle Transportation Management integration is active for the client.
• Grouping flags — GROUP_BY_CUSTOMER_FLAG, GROUP_BY_FREIGHT_TERMS_FLAG, GROUP_BY_FOB_FLAG, GROUP_BY_SHIP_METHOD_FLAG.
• LPN attributes — LPN_PREFIX, LPN_SUFFIX, UCC_128_SUFFIX_FLAG, TOTAL_LPN_LENGTH, LPN_STARTING_NUMBER.
• Descriptive flexfield columns — ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical uses include auditing ship confirmation configuration per client, validating LPN numbering setup, and supporting integrations that require human-readable rule and routing names.

• Retrieve ship confirm rule assignments for all clients.
• Filter clients where OTM integration is enabled.
• Review LPN labeling parameters for a specific trading partner.

Sample query:

SELECT client_id, client_name, ship_confirm_rule_name, routing_name, otm_enabled, lpn_prefix, total_lpn_length FROM apps.mtl_client_parameters_v WHERE ship_confirm_rule_name IS NOT NULL;

Sample query filtered by client code:

SELECT client_code, client_name, ship_confirm_rule_id, ship_confirm_rule_name FROM apps.mtl_client_parameters_v WHERE client_code = :p_client_code;