Search Results wip_mti_pub




Overview
Explore in AI Chat

Overview

APPS.WIP_MTI_PUB is a public PL/SQL package within the Oracle E-Business Suite Work in Process (WIP) module. Its name reflects its role as a public-facing interface for "Material Transaction Interface" processing associated with WIP transactions. The package serves as a supporting API layer for the Oracle Inventory transaction management infrastructure, specifically handling the validation and processing of material transactions that flow through the MTL_TRANSACTIONS_INTERFACE (MTI) table in the context of Work in Process discrete jobs and related entities.

Rather than representing a standalone user-facing business function, WIP_MTI_PUB functions as an internal orchestration and validation utility invoked during inventory and WIP transaction processing. Its classification as a PUB (public) package means it is exposed to other application modules and is intended to be referenced programmatically. The package carries a VALID status in the ETRM repository, confirming it compiles successfully and is available for use in Oracle EBS 12.1.1 and 12.2.2 environments.

Key Procedures and Functions

The ETRM metadata documents five procedures or functions within WIP_MTI_PUB. Each is described below by purpose only:

  • PREINVWIPPROCESSING — Performs preparatory processing for inventory/WIP transaction interface records before the main inventory validation stages. It establishes the context required for subsequent validation and posting operations.
  • VALIDATEINTERFACEROWS — Validates the rows residing in the material transactions interface tables, applying business rules around items, revisions, kanban cards, reservations, and other related WIP and inventory entities. This is a core validation step that determines whether interface rows are eligible for processing.
  • POSTINVWIPVALIDATION — Handles validation activities executed after the principal inventory/WIP processing has occurred. It confirms post-processing correctness and identifies any residual inconsistencies.
  • POSTINVWIPPROCESSING — Carries out the final processing actions for inventory and WIP transactions following validation, including any necessary cleanup or confirmation steps.
  • SETMTIERROR — Records error information against material transaction interface rows when validation or processing fails, enabling users to diagnose and correct rejected transactions.

The precise parameter signatures of these procedures are not exposed in the supplied metadata and should not be assumed.

Tables Accessed

The package accesses a documented set of tables via APPS synonyms. Interface and transaction tables such as MTL_TRANSACTIONS_INTERFACE and MTL_MATERIAL_TRANSACTIONS_S form the primary processing surface, with MTL_TRANSACTION_TYPES supplying transaction type definitions and MTL_PARAMETERS providing inventory control settings. Item and revision validation relies on MTL_SYSTEM_ITEMS, MTL_SYSTEM_ITEMS_KFV, MTL_ITEM_REVISIONS, MTL_ITEM_REVISIONS_B, and ENG_REVISED_ITEMS. WIP-specific context is drawn from WIP_DISCRETE_JOBS and WIP_ENTITIES. Kanban-driven transactions are supported through MTL_KANBAN_CARDS and MTL_KANBAN_CARD_ACTIVITY, while MTL_RESERVATIONS and MTL_SECONDARY_INVENTORIES support reservation and subinventory validation logic.

Usage Notes

WIP_MTI_PUB is invoked indirectly by higher-level transaction management packages rather than called directly by end users. The dependency metadata confirms it is referenced by INV_TXN_MANAGER_PUB and WIP_FLOWUTIL_PRIV, both of which form part of the standard transaction processing chain. It is also self-referencing, indicating internal recursive or re-entrant calls. Typical invocation occurs when the material transaction manager processes interface records—such as during the Transaction Manager concurrent program, move transaction processing in WIP discrete manufacturing, or backflush and kanban replenishment flows. Custom code integrating with WIP transaction interfaces may reference this package, but because it is an internal orchestration API, Oracle does not guarantee its signature across releases; developers should prefer documented public APIs where available and use WIP_MTI_PUB only with an understanding of its supporting role in interface validation and posting.