Search Results validate_qty_for_ib

Overview

The APPS.GME_INCREMENTAL_BACKFLUSH_PVT package is a private PL/SQL API within the Oracle E-Business Suite Process Manufacturing (OPM) module. It is classified as a PVT package, indicating that it serves as an internal implementation component rather than a public-facing interface. Its principal business function is to execute incremental backflush processing against released process manufacturing batches. Rather than consuming all required ingredients at batch release, incremental backflush allows material to be issued progressively as production progresses through the batch steps, producing a more accurate consumption picture aligned with actual shop-floor activity.

The package encapsulates the validation, quantity derivation, step dependency resolution, and transaction creation logic required to issue component materials incrementally. It reads batch configuration and step sequencing from the GME production tables, converts quantities into the appropriate primary and secondary units of measure, and creates inventory material transactions. In Oracle EBS 12.1.1 and 12.2.2, this package remains a foundational element of the OPM backflush engine and is invoked indirectly whenever incremental backflush is triggered through the public OPM APIs.

Key Procedures and Functions

The package exposes seven documented procedures and functions:

• INCREMENTAL_BACKFLUSH — The primary driver routine. It orchestrates the incremental backflush operation for a batch, coordinating validation, quantity derivation, transaction generation, and step updates.
• DERIVE_FACTOR — Computes the proportional factor used to determine how much of each component material should be consumed at the current incremental point relative to the total batch quantity.
• UPDATE_DEPENDENT_STEPS — Updates the status of batch steps whose execution depends on the completed backflush activity, ensuring step dependency logic remains consistent.
• REVERT_MATERIAL_PARTIAL — Handles reversal of partially consumed material transactions when an incremental backflush must be rolled back or corrected.
• VALIDATE_MATERIAL_FOR_IB — Verifies that a given material is eligible for incremental backflush, checking item and batch attributes before processing proceeds.
• VALIDATE_QTY_FOR_IB — Confirms that the requested backflush quantity is valid against available batch and material quantities.
• GET_CONVERTED_QTY — Returns quantities converted between the batch's primary unit of measure and an alternate or secondary unit of measure to support consistent transaction creation.

Tables Accessed

The package reads and writes a broad set of OPM and inventory tables through APPS synonyms:

• GME_BATCH_HEADER — Batch header information, used to identify the batch, its status, and its controlling parameters.
• GME_MATERIAL_DETAILS — Component material requirements and consumption details for the batch.
• GME_BATCH_STEPS, GME_BATCH_STEP_ACTIVITIES, GME_BATCH_STEP_DEPENDENCIES, GME_BATCH_STEP_ITEMS, GME_BATCH_STEP_RESOURCES — Step-level definitions, sequencing, dependencies, items, and resources used when determining what to backflush and in what order.
• GME_PARAMETERS — System and batch parameters governing backflush behavior.
• GME_RESOURCE_TXNS_GTMP — Global temporary table used for staging resource transaction data during processing.
• MTL_MATERIAL_TRANSACTIONS, MTL_SYSTEM_ITEMS, MTL_SYSTEM_ITEMS_KFV, MTL_TRANSACTION_LOT_NUMBERS — Inventory tables used to create material issues, validate items, and capture lot information.
• PLITBLM — PL/SQL table used internally for array processing.

Usage Notes

As a PVT package, GME_INCREMENTAL_BACKFLUSH_PVT is not intended for direct invocation by end users or custom code. It is referenced by GME_API_MAIN and GME_API_PUB, which are the public API entry points for OPM batch operations. Consequently, incremental backflush is triggered indirectly through these public APIs, typically from OPM batch processing forms, shop-floor execution, or concurrent programs that manage batch release and completion. Customizations should call the public packages rather than this private implementation, since its procedures may change between releases. Direct dependencies include GME_COMMON_PVT and standard Oracle utilities such as SYS.STANDARD. Because the package writes to MTL_MATERIAL_TRANSACTIONS, any invocation produces real inventory transactions and must be executed within a properly committed transaction scope.