Search Results ship_unspecified_action_flag

Overview

APPS.WSH_SHIP_CONFIRM_RULES_V is an internal Oracle E-Business Suite view owned by the APPS schema and registered under FND Design Data as WSH.WSH_SHIP_CONFIRM_RULES_V. It belongs to the Oracle Shipping Execution (WSH) product family and presents ship confirmation rules — the configurable business rules that determine how shipment confirmations are processed, staged, interfaced, and documented. The view has a status of VALID and is classified in the ETRM repository as an internal view.

The view exposes a denormalized, reporting-friendly projection of ship confirmation rule definitions. Rather than requiring callers to resolve code values against lookups directly, it surfaces descriptive attributes alongside coded flags, including the resolved shipment method name. This makes it particularly suitable for reconciliation and diagnostic queries. Oracle explicitly marks the object as Oracle Internal Use Only, meaning direct access is unsupported except through standard Oracle Applications programs; the view is nonetheless widely referenced in ad hoc diagnostics because of its readable column set.

Underlying Base Objects

According to the documented ETRM metadata, WSH_SHIP_CONFIRM_RULES_V references the following objects:

• FND_LOOKUP_VALUES_VL (VIEW) — the multilingual lookup values view, used to decode flag and code columns into meaningful descriptions, including shipment method names.
• WSH_REPORT_SETS (SYNONYM) — source of document/report set information referenced by DOCUMENT_SET_NAME and REPORT_SET_ID.
• WSH_SHIP_CONFIRM_RULES (SYNONYM) — the principal base table holding ship confirmation rule definitions; the view's SHIP_CONFIRM_RULE_ID maps to the primary key of this table.

The view therefore functions as a join layer: the base rule record from WSH_SHIP_CONFIRM_RULES is enriched with lookup-derived display values and report set metadata, producing a single row per effective ship confirmation rule.

Key Columns

• SHIP_CONFIRM_RULE_ID — primary key of the rule; joins back to the base table.
• NAME — the user-defined rule name (VARCHAR2(30)).
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — date range during which the rule is active.
• ACTION_FLAG / ACTION_FLAG_UI / SHIP_UNSPECIFIED_ACTION_FLAG — control how confirmations and unspecified shipments are acted upon.
• SHIP_METHOD_NAME (VARCHAR2(80)) / SHIP_METHOD_CODE (VARCHAR2(30)) — the shipment method description and code resolved for the rule. This is the column most commonly searched by users and is populated from lookup decoding.
• SHIP_METHOD_DEFAULT_FLAG / STAGE_DEL_FLAG — indicate whether the shipment method is defaulted and whether staged deliveries are handled.
• AC_* columns (AC_ACTUAL_DEP_DATE_DEFAULT, AC_INTRANSIT_FLAG, AC_CLOSE_TRIP_FLAG, AC_BOL_FLAG, AC_DEFER_INTERFACE_FLAG) — auto-confirm behavior settings.
• MC_* columns (MC_INTRANSIT_FLAG, MC_CLOSE_TRIP_FLAG, MC_DEFER_INTERFACE_FLAG, MC_BOL_FLAG) — manual-confirm behavior settings.
• DOCUMENT_SET_NAME / REPORT_SET_ID — document set used when printing shipping documents.
• SEND_945_FLAG — indicates whether an EDI 945 (warehouse shipping advice) is transmitted.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY.

Common Use Cases and Queries

Typical uses include auditing active ship confirmation rules, verifying which shipment method a rule defaults to, and tracing document set and 945 interface behavior. A common query filters on the search term ship_method_name:

• SELECT ship_confirm_rule_id, name, ship_method_name, ship_method_code, effective_start_date, effective_end_date FROM apps.wsh_ship_confirm_rules_v WHERE ship_method_name LIKE '&method%' ORDER BY name;
• SELECT name, ship_method_name, action_flag, send_945_flag, document_set_name FROM apps.wsh_ship_confirm_rules_v WHERE SYSDATE BETWEEN effective_start_date AND NVL(effective_end_date, SYSDATE + 1);

Because access is documented as internal only, such queries should be confined to diagnostics and reporting, not custom application logic.