Search Results ship_method_default_flag

Overview

WSH_SHIP_CONFIRM_RULES_V is an APPS-owned, VALID database view in the WSH – Shipping Execution module of Oracle E-Business Suite 12.1.1 and 12.2.2. It presents shipping confirmation rule definitions in a denormalized, presentation-ready form. Shipping confirmation rules stored in the base table WSH_SHIP_CONFIRM_RULES govern the behavior that occurs when a delivery or trip is ship-confirmed, including whether an actual departure date is defaulted, whether the trip is closed, whether intransit inventory is updated, whether a bill of lading is generated, and whether the accounting (AC) or manufacturing (MC) interface is deferred.

The view's role in reporting and integration is to expose these rules together with the resolved ship method name and report set name, so that reports, concurrent programs, and interface logic can read rule attributes without performing the same lookup and report-set joins repeatedly. Because Oracle's shipping confirmation engine depends heavily on rule setup, this view is a convenient read-only surface for administrators and technical consultants validating configuration, and for custom extracts that need to know how a given rule will drive ship-confirm processing.

The user's search term, AC_DEFER_INTERFACE_FLAG, corresponds directly to a column exposed by this view. It is one of two parallel deferral flags, alongside MC_DEFER_INTERFACE_FLAG, and it determines whether the accounting interface is deferred when the rule's action is executed.

Underlying Base Objects

The view is defined over three documented base objects:

• WSH_SHIP_CONFIRM_RULES (referenced as a SYNONYM) — the primary source of all rule attributes, joined on SHIP_CONFIRM_RULE_ID and providing the rule identity, effectivity dates, action flag, ship method code, and the accounting, manufacturing, BOL, and interface-related flags.
• WSH_REPORT_SETS (referenced as a SYNONYM) — an outer-joined source supplying the report set name (RS.NAME) for the rule's REPORT_SET_ID. Because the join is outer (+), a rule without an assigned report set still appears in the view with a null report set name.
• FND_LOOKUP_VALUES_VL (referenced as a VIEW) — an outer-joined lookup source that resolves SHIP_METHOD_CODE to its meaning via LOOKUP_TYPE = 'SHIP_METHOD' and VIEW_APPLICATION_ID = 3. This supplies the SHIP_METHOD_NAME column.

The view performs no aggregation or filtering; it is a pure projection of the rule row with two outer-joined descriptive lookups. The DECODE expressions translate ACTION_FLAG into normalized ACTION_FLAG_UI and SHIP_UNSPECIFIED_ACTION_FLAG values (for example, 'B', 'T', and 'L' all map to 'S' for one decoded column), so consumers can interpret the rule action consistently regardless of the internal flag value stored.

Key Columns

• SHIP_CONFIRM_RULE_ID — primary identifier of the shipping confirmation rule.
• NAME — user-defined rule name.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date range during which the rule is active.
• ACTION_FLAG, ACTION_FLAG_UI, SHIP_UNSPECIFIED_ACTION_FLAG — the rule action and its decoded presentation equivalents.
• SHIP_METHOD_CODE / SHIP_METHOD_NAME — the ship method the rule applies to, and its resolved lookup meaning.
• AC_ACTUAL_DEP_DATE_DEFAULT — controls defaulting of the actual departure date for accounting purposes.
• AC_INTRANSIT_FLAG / MC_INTRANSIT_FLAG — indicate whether intransit processing applies to the accounting and manufacturing flows respectively.
• AC_CLOSE_TRIP_FLAG / MC_CLOSE_TRIP_FLAG — control trip closure behavior for each flow.
• AC_BOL_FLAG / MC_BOL_FLAG — control bill of lading generation.
• AC_DEFER_INTERFACE_FLAG — determines whether the accounting interface is deferred when the rule action executes; the corresponding MC_DEFER_INTERFACE_FLAG does the same for the manufacturing interface.
• STAGE_DEL_FLAG — governs staging/delivery handling behavior.
• SEND_945_FLAG — indicates whether an EDI 945 (warehouse shipping advice) should be sent.
• REPORT_SET_ID / DOCUMENT_SET_NAME — the assigned report set and its resolved name.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — standard auditing columns.

Common Use Cases and Queries

A typical administrative query lists the rules relevant to a ship method, showing the deferral and intransit flags that determine integration behavior:

SELECT name, ship_method_code, ship_method_name,
  ac_defer_interface_flag, mc_defer_interface_flag,
  ac_intransit_flag, mc_intransit_flag,
  effective_start_date, effective_end_date
FROM apps.wsh_ship_confirm_rules_v
WHERE ship_method_code = :p_ship_method
ORDER BY name;

To isolate rules where the accounting interface is deferred, which is often done when reconciling why accounting entries were not generated at ship confirm:

SELECT ship_confirm_rule_id, name, ship_method_code, action_flag_ui
FROM apps.wsh_ship_confirm_rules_v
WHERE ac_defer_interface_flag = 'Y';

To check rule-to-report-set assignment for document generation, including rules with no report set due to the outer join:

SELECT name, ship_method_code, document_set_name
FROM apps.wsh_ship_confirm_rules_v
WHERE report_set_id IS NULL;

Because the view also exposes the accounting and manufacturing flag families side by side, it is well suited to configuration audits and to custom reports that compare AC versus MC processing behavior per rule. As with any APPS view, queries should be executed against the APPS schema or a reporting account granted SELECT on it.