Results for “receipt_asn_exists_code”

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

Overview

MTL_CLIENT_PARAMETERS_V is an Oracle E-Business Suite Inventory (INV) reporting view owned by the APPS schema. It presents client-level receiving and shipping control parameters maintained in the MTL_CLIENT_PARAMETERS table, enriched with descriptive attributes drawn from Oracle Receiving, Oracle Shipping Execution, and Oracle Trading Community Architecture (HZ) tables. The view consolidates configuration data that governs inbound receipt processing, advance ship notice (ASN) behavior, RMA routing, delivery grouping, ship confirmation, and license plate number (LPN) generation for a given client (trading partner).

The view is primarily used for reporting, data extraction, and integration scenarios requiring resolved, human-readable values rather than raw identifiers. While the underlying configuration is stored in MTL_CLIENT_PARAMETERS, the view resolves party names, routing names, ship confirm rule names, and delivery report set names, eliminating the need for downstream join logic. The inclusion of the CLIENT_NUMBER column makes the view a natural reference point for queries searching on client_number, since that identifier appears directly in the view's SELECT list.

Underlying Base Objects

The view is defined over the following documented base objects:

• MTL_CLIENT_PARAMETERS (SYNONYM) — the primary source table, aliased CLIENT_PARAM within the view text, supplying all client parameter columns including CLIENT_NUMBER.
• HZ_PARTIES (SYNONYM) — joined to derive CLIENT_NAME (exposed as PARTIES.PARTY_NAME).
• HZ_CUST_ACCOUNTS (SYNONYM) — referenced in the TCA join path linking the client to its party record.
• RCV_ROUTING_HEADERS (VIEW) — supplies ROUTING_NAME for the RMA_RECEIPT_ROUTING_ID.
• WSH_SHIP_CONFIRM_RULES (SYNONYM) — supplies SHIP_CONFIRM_RULE_NAME via SHIP_CONF_RULE.NAME.
• WSH_REPORT_SETS (SYNONYM) — supplies SHIP_CONFIRM_DOCUMENT_SET_NAME via REPORT_SET.NAME.

Key Columns

• ROW_ID — the physical ROWID of the underlying MTL_CLIENT_PARAMETERS row.
• CLIENT_ID / CLIENT_CODE / CLIENT_NAME / CLIENT_NUMBER — client identification; CLIENT_NUMBER is the user-facing trading partner number and the column most frequently searched.
• TRADING_PARTNER_SITE_ID — the associated trading partner site.
• RECEIPT_ASN_EXISTS_CODE — indicates ASN-based receipt behavior.
• RMA_RECEIPT_ROUTING_ID / ROUTING_NAME — RMA receipt routing and its resolved name.
• GROUP_BY_*_FLAG — grouping flags for customer, freight terms, FOB, and ship method.
• OTM_ENABLED — Oracle Transportation Management integration flag.
• SHIP_CONFIRM_RULE_ID / SHIP_CONFIRM_RULE_NAME — ship confirmation rule.
• AUTOCREATE_DEL_ORDERS_FLAG and DELIVERY_REPORT_SET_ID / SHIP_CONFIRM_DOCUMENT_SET_NAME — delivery order and document set settings.
• LPN_PREFIX, LPN_SUFFIX, UCC_128_SUFFIX_FLAG, TOTAL_LPN_LENGTH, LPN_STARTING_NUMBER — LPN generation parameters.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–15 — descriptive flexfield columns.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — audit columns.

Common Use Cases and Queries

Typical uses include validating client receiving parameters, auditing ship confirmation configuration, verifying LPN numbering schemes, and feeding integration extracts. A common lookup is retrieval of parameters by client number:

• SELECT client_id, client_code, client_name, client_number, ship_confirm_rule_name, lpn_prefix, lpn_suffix
• FROM apps.mtl_client_parameters_v
• WHERE client_number = :p_client_number;

Reporting clients with LPN control:

• SELECT client_number, client_name, lpn_prefix, total_lpn_length
• FROM apps.mtl_client_parameters_v
• WHERE lpn_prefix IS NOT NULL;

The view should be treated as read-only configuration reference data; parameter changes are made through the Inventory receiving and shipping setup forms, not directly against the view.