Results for “invalid_status”

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

Overview

WSH_TRANSACTIONS_HISTORY_PKG is a shipping-execution package in Oracle E-Business Suite (EBS) Release 12.1.1 and 12.2.2 that maintains the transaction history audit trail for the Oracle Shipping (WSH) module. Every significant action performed against a delivery, trip, or shipping document — confirm, ship, cancel, pack, manifest, and similar events — is recorded in WSH_TRANSACTIONS_HISTORY so that users can trace the lifecycle of a shipment. This package is the central API for creating and querying those history rows. It is owned by APPS and classified under ETRM as OTHER, with three documented procedures: CREATE_UPDATE_TXNS_HISTORY, GET_TXNS_HISTORY, and CREATE_TXNS_HISTORY.

Key Procedures and Functions

• CREATE_UPDATE_TXNS_HISTORY — The main entry point. It accepts an IN OUT transaction-history record and returns the transaction identifier along with a return status. Internally it performs an existence check against WSH_TRANSACTIONS_HISTORY keyed on document type, document number, direction, action type, entity number/type, and trading partner, then either inserts a new history row or updates the existing one. The source excerpt shows dedicated exceptions for invalid_status, invalid_action, invalid_entity_type, invalid_direction, and invalid_document_type, confirming that the procedure validates the incoming action/status combinations before writing. It also contains logic (the c_get_del_status cursor) to derive delivery status codes from WSH_NEW_DELIVERIES, and it accumulates warning and error counts using WSH_INTERFACE_VALIDATIONS_PKG.
• GET_TXNS_HISTORY — A retrieval routine used to fetch existing transaction-history records, typically for display in shipping inquiry screens or for validation by calling processes.
• CREATE_TXNS_HISTORY — A creation-oriented wrapper that records a transaction-history entry when a shipping action occurs.

Note that no parameter lists are invented here; the documented procedures are described by purpose only.

Tables Accessed

• WSH_TRANSACTIONS_HISTORY — The primary table; read (for the existence check and delivery-status cursor) and written (insert/update) by the package.
• WSH_NEW_DELIVERIES — Joined to resolve delivery name and status code for a document number.
• WSH_NEW_DEL_INTERFACE — Interface table involved in shipping validation and delivery processing.
• WSH_TRANSACTION_S (WSH_TRANSACTIONS) — Supplies transaction identifiers and statuses referenced during history creation.
• DUAL — Used for single-row checks and sequence-style lookups.

Usage Notes

This package is invoked internally by Oracle Shipping flows — delivery confirmation, ship confirm, trip processing, and manifesting — rather than directly by end users. It is referenced by nine other APPS packages, indicating it is a dependency for higher-level shipping APIs and concurrent programs. Given the presence of formal exception handlers such as invalid_status, callers should expect status-validation errors when a requested action is not legal for the current document state. Because the procedure uses SELECT ... FOR UPDATE NOWAIT on history rows, concurrency conflicts can raise ORA-00054 under heavy multi-user shipping activity. Customizations should call CREATE_UPDATE_TXNS_HISTORY rather than writing to WSH_TRANSACTIONS_HISTORY directly, ensuring the same validation and status-derivation logic applied by standard EBS 12.1.1 and 12.2.2 functionality.