Search Results details_required




Overview
Explore in AI Chat

Overview

WSH_SC_DETAILS_REQUIRED_PKG is a shipping execution package within the Oracle E-Business Suite Logistics module. Its purpose, as stated in the package header, is to determine whether details are required during the Ship Confirm process. The package exists to evaluate business conditions that dictate whether a user performing ship confirmation must enter detailed information — such as lot, serial, or revision numbers — for the items being shipped, or whether the transaction can proceed with header-level defaulting only.

This determination is significant because shipping operations span a wide range of item types and order categories. Controlled items, for example, may mandate per-line detail capture, while non-controlled finished goods may not. By encapsulating the logic that inspects entity state, warehouse configuration, reservations, and order category, the package provides a single, reusable decision point for the Ship Confirm flow rather than embedding conditional logic in multiple places. The package is declared with AUTHID CURRENT_USER and is owned by APPS, making it a standard component of the shipping application schema. Its original header comment, dated July 1999 and credited to troveda with a creation date of March 1997, indicates that this logic has been a stable part of shipping execution since the earliest releases of the module.

Key Procedures and Functions

The package exposes a single documented public procedure:

  • DETAILS_REQUIRED — Evaluates whether a particular ship-confirmation batch requires details, returning the outcome through an output parameter. As documented, the procedure accepts an entity identifier, a mode, an action, a reservation indicator, a warehouse identifier, and an order category as inputs, and returns a value indicating whether details are required. The procedure is the sole entry point into this package, and calling applications rely on its return to branch between a detailed confirmation screen flow and an automatic, header-level confirmation flow.

Tables Accessed

The documented metadata lists DBMS_SQL as the referenced database object via APPS synonyms. This indicates that the package uses dynamic SQL to resolve its underlying queries at runtime rather than referencing fixed shipping tables statically. The use of dynamic SQL is consistent with a decision routine whose queries may vary by mode, action, or warehouse context — for example, allowing the procedure to interrogate shipping or inventory configuration tables that differ by setup or that are not known until execution.

No static application tables are documented as directly referenced. The procedure argues its case entirely on the inputs supplied by the caller, combined with whatever configuration data it resolves dynamically through DBMS_SQL.

Usage Notes

WSH_SC_DETAILS_REQUIRED_PKG is invoked as part of the Ship Confirm workflow, typically in one of two circumstances:

  • Ship Confirm forms and concurrent programs — The shipping execution UI calls the procedure before presenting the confirmation screen. If details are required, the user is directed to the detailed confirmation interface; if not, the transaction is confirmed without user intervention at line-detail level.
  • Custom or extension code — Because the package is granted to APPS and designed as a public decision point, custom ship-confirm extensions or interfaces may call DETAILS_REQUIRED to reproduce the same determination logic consistently.

Callers must pass the full set of documented inputs — entity, mode, action, reservations, warehouse, and order category — since the procedure's evaluation depends on the combination of these values. Because the return parameter is IN OUT, callers should initialize it before invocation. The documented metadata records no dependencies from other packages, so this package is a leaf-level utility within the shipping execution stack.