Search Results xc_tab_type

Overview

WSH_EXCEPTIONS_GRP is a PL/SQL grouping package (API classification GRP) owned by APPS in the Oracle E-Business Suite. It encapsulates the business logic used by Oracle Shipping Execution to capture, query, and act upon shipping exceptions. In shipping operations, an exception represents a deviation from expected execution flow — a short-shipped delivery, a missing container, a staging shortfall, a lot or serial mismatch, or any other condition that prevents a delivery detail from being processed as planned. This package provides the programmatic scaffolding that lets calling code retrieve the exceptions associated with a delivery, trip, stop, or container and then record, transition, or purge them.

Two strongly typed PL/SQL record definitions are declared in the package specification. XC_REC_TYPE carries the minimal identity of an exception instance — exception_id, exception_name, and status. The larger XC_ACTION_REC_TYPE is the working structure used when logging, changing status, or purging exceptions. It includes a request_id (also used for purge), batch_id, the full exception identity and logging entity context (logging_entity and logging_entity_id), a manually_logged flag, message, location codes, severity, delivery and trip names, stop and delivery detail identifiers, container name, org_id, inventory_item_id, and the item description columns lot_number, revision, serial_number, units of measure, quantities, subinventory, locator_id, error_message, and the fifteen descriptive flexfield attribute columns. These definitions indicate that the package is the canonical in-memory representation of a shipping exception across the Shipping Execution module.

Key Procedures and Functions

Two documented procedures constitute the public interface of WSH_EXCEPTIONS_GRP:

• GET_EXCEPTIONS — Retrieves exception records for a given business context. Callers use it to populate the XC_REC_TYPE/XC_ACTION_REC_TYPE structures with the exception identifiers and names applicable to a delivery, trip, stop, or container, so that downstream validation or display logic can evaluate them. The search term "xc_tab_type" relates to this area of the interface, specifically the PL/SQL table type used to hold and pass collections of the XC record structures between program units.
• EXCEPTION_ACTION — Performs the action verbs on exceptions. Based on the fields it consumes, it supports logging a new exception, purging existing exceptions, and changing the status of an exception. It accepts the full XC_ACTION_REC_TYPE payload, including message text, severity, location codes, and flexfield attributes, and persists the resulting state to the shipping exception tables. It is the single entry point for creating or updating exception state rather than writing directly to WSH_EXCEPTIONS.

Both procedures are declared in the package and are the only documented members of the API surface; no parameter lists are reproduced here because the specification excerpt does not enumerate them.

Tables Accessed

The package operates against the following documented tables (referenced through APPS synonyms):

• WSH_EXCEPTIONS — the transactional exception table where logged exceptions, status, severity, and attribute data are stored and later purged.
• WSH_EXCEPTION_DEFINITIONS_TL — the translated definition table that supplies exception_name and related descriptive information for the installed exception codes.
• WSH_DELIVERY_DETAILS — the delivery detail records against which exceptions are raised, supplying delivery_detail_id, item, quantity, lot, and revision context.
• WSH_NEW_DELIVERIES — the delivery header/current-delivery view used to resolve delivery_name and the associated trip and stop context.
• PLITBLM — the standard EBS PL/SQL table-of-varchar2 utility used by the API for handling list or array parameters, the mechanism most closely associated with the "xc_tab_type" search term.

Usage Notes

WSH_EXCEPTIONS_GRP is an internal Shipping Execution API. It is invoked by the Shipping Transactions and Delivery Exception windows in Oracle Forms, by Shipping Execution concurrent programs such as the Pick Release and shipping exception reports, and by other shipping packages — the ETRM metadata records that three other packages reference it. Customizations that need to raise or resolve a shipping exception should call EXCEPTION_ACTION rather than inserting into WSH_EXCEPTIONS directly, and should use GET_EXCEPTIONS to query existing state. Because the record type carries org_id, multi-org filtering is expected from the caller. The package header dates from release 12.0 and remains the supported interface in 12.1.1 and 12.2.2; note that the specification is a grouping shell with no versioning body, so callers should always obtain exception definitions from WSH_EXCEPTION_DEFINITIONS_TL to avoid hard-coding names.