Results for “organization_id”

50+ results




Overview
Explore in AI Chat

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

Overview

WIP_MOVE_VALIDATOR is a server-side PL/SQL package body in the APPS schema that provides validation and error-logging services for Work in Process (WIP) move transactions submitted through the open transaction interface. Its principal role is to inspect move transaction records staged in the WIP_MOVE_TXN_INTERFACE table, confirm that each transaction conforms to Oracle Manufacturing business rules, and record any failures into the WIP_TXN_INTERFACE_ERRORS table so that the submitting process or user can correct and resubmit them. The package is classified as an "OTHER" API in ETRM 12.2.2 and is referenced by one other package, indicating its role as a shared validation utility rather than a directly callable public interface.

A recurring search term associated with this object is add_error, which reflects the package's dual purpose: it validates transactions and it captures descriptive errors for every invalid record. Because the package owns both responsibilities internally, callers need not implement their own error collection logic.

Key Procedures and Functions

  • ADD_ERROR — overloaded error handler. One form accepts a single transaction identifier together with an error column and error message and appends a request_error record to the package-level current_errors collection. A second, optimized form accepts a list of transaction identifiers (txnID_list) and creates one error record per identifier, applying the column and message to all of them. The message text is truncated to 240 bytes before storage.
  • LOAD_ERRORS — iterates the in-memory current_errors collection and inserts each entry into WIP_TXN_INTERFACE_ERRORS, populating the standard WHO columns, request identifier, and program identifiers so errors are traceable to the originating concurrent request.
  • VALIDATE — the primary validation entry point. It evaluates staged move transactions against the documented reference tables and raises errors through ADD_ERROR.
  • ORGANIZATION_ID — resolves or confirms the inventory organization context for the transaction under validation.
  • MOVE_TXN_TYPE and GET_MOVE_TXN_TYPE — determine and return the move transaction type, distinguishing among the supported move transaction semantics.
  • VALIDATEOATXN — a supplementary validation routine targeting the operational/assembly transaction aspects of a move.

All eight documented programs are declared inside the package body; no separate specification exposes them for arbitrary external use.

Tables Accessed

The package reads transactional and reference data and writes error diagnostics. WIP_MOVE_TXN_INTERFACE is the source staging table from which move transactions are read. MTL_SYSTEM_ITEMS and MTL_SYSTEM_ITEMS_KFV supply item master attributes and concatenated descriptions; MTL_PARAMETERS provides organization-level defaults; MTL_ITEM_REVISIONS, MTL_LOT_NUMBERS, and MTL_SERIAL_NUMBERS support revision, lot, and serial validation. MTL_MATERIAL_TRANSACTIONS and MTL_OBJECT_GENEALOGY are consulted for transaction history and genealogy context. BOM_DEPARTMENTS and BOM_STANDARD_OPERATIONS provide routing and department references, HR_ORGANIZATION_INFORMATION supplies organization classification, and FND_USER and GL_CODE_COMBINATIONS supply user and accounting references. MTL_TRANSACTION_REASONS validates reason codes. The only documented write target is WIP_TXN_INTERFACE_ERRORS, populated by LOAD_ERRORS.

Usage Notes

WIP_MOVE_VALIDATOR is not intended for direct invocation by end users or casual custom code. It is invoked in the context of the WIP move transaction interface, typically from the Manufacturing Open Interface concurrent program or from the WIP Material Transactions form when transactions are submitted for processing. Custom code that deliberately stages rows into WIP_MOVE_TXN_INTERFACE should run the standard validation flow rather than calling individual procedures, so that errors are accumulated and persisted consistently by ADD_ERROR and LOAD_ERRORS. Because error rows are keyed to the concurrent request, DBAs and support analysts should query WIP_TXN_INTERFACE_ERRORS by transaction_id to diagnose failures. The package header revision 120.12 (2007) confirms the logic is stable across 12.1.1 and 12.2.2, with the multi-transaction ADD_ERROR overload introduced specifically to avoid redundant assignments inside loops.