Results for “tracking_quantity_ind”

50+ results




Overview
Explore in AI Chat

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

Overview

INV_STATUS_PKG is an Oracle Applications (APPS) PL/SQL package that encapsulates material status management logic within the Oracle Inventory module of Oracle E-Business Suite. Material statuses in EBS control the usability and transaction eligibility of on-hand inventory, lots, serial numbers, and locators. This package provides the programmatic interface through which material status changes are validated, applied, and recorded across the affected inventory entities.

The package operates in both 12.1.1 and 12.2.2 environments and carries a VALID status in the ETRM repository. It is classified as an "OTHER" API type rather than a public open interface or a formalized public API, which means it is primarily intended for internal consumption by Oracle Inventory forms, workflows, and dependent product code rather than as a supported customer extension point. It references the SYS.STANDARD package and is referenced by several other objects, including GMD_SAMPLES_GRP, MTL_MATERIAL_STATUS_HIST_ERV, and by itself through recursive invocation.

Key Procedures and Functions

The package exposes ten documented procedures and functions that collectively cover status retrieval, status validation, status assignment, and status history processing:

  • GET_FROM_STATUS_CODE — Retrieves the originating (from) material status code associated with a status change context, supporting audit and history reconstruction.
  • GET_ONHAND_FROM_STATUS — Returns the prior on-hand material status for a given inventory entity, used to determine the starting status before an update.
  • CHECK_LOT_RANGE_STATUS — Validates lot numbers against status rules, ensuring that lot-level status restrictions are respected before a status operation proceeds.
  • CHECK_SERIAL_RANGE_STATUS — Performs the equivalent validation for serial-number-controlled inventory, confirming serial ranges comply with material status constraints.
  • POST_SIGN_CHANGES — Posts quantity sign changes associated with status transitions, reflecting additions or removals of quantity from status-controlled buckets.
  • UPDATE_STATUS — The core status-update routine; applies a new material status to the target inventory entity and drives associated validations.
  • INVOKE_REASON_WF — Invokes the reason workflow, launching the Oracle Workflow process associated with a material status change reason.
  • TRACKING_QUANTITY_IND — Returns the tracking quantity indicator, determining whether quantity is tracked for the status context in question.
  • GET_MIXED_STATUS — Evaluates and returns mixed-status information where an inventory entity contains items in differing statuses.
  • GET_MIXED_STATUS_SERIAL — Returns mixed-status information specifically for serial-number-controlled inventory.

Parameter lists are not documented in the available metadata and are therefore not reproduced here.

Tables Accessed

The package reads and writes against the core Oracle Inventory and Warehouse Management tables, accessed through APPS synonyms:

Usage Notes

INV_STATUS_PKG is invoked indirectly rather than directly by end users. The principal callers are the Oracle Inventory material status forms (such as the Change Material Status and View Material Status windows), the MTL_MATERIAL_STATUS_HIST_ERV concurrent program that produces status-change reporting, and GMD_SAMPLES_GRP in the Process Manufacturing suite. The presence of INVOKE_REASON_WF indicates integration with Oracle Workflow for reason-driven status changes.

Because the package is classified as OTHER rather than a public API, custom development should avoid calling these routines directly where a supported interface exists; changes to MTL_MATERIAL_STATUS_HISTORY should instead be driven through the standard Inventory forms to ensure that the package's validation, lot/serial range checking, and mixed-status logic are consistently applied. Direct calls risk bypassing workflow invocation and history logging, producing inconsistent audit records.