Results for “status_check”
12 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
INV_KANBAN_PKG is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite (validated against 12.1.1 and 12.2.2). Its documented API classification is OTHER, indicating it is a supporting/internal utility package rather than a formally published public interface. The package underpins the Oracle Inventory Kanban replenishment feature, which governs how material is pulled through the shop floor and supplier network using kanban cards, pull sequences, and replenishment signals. It supplies the data-handling and validation logic that the Kanban Workbench and related inquiry forms require: resolving organization and locator names, determining replenishment source types, retrieving supplier and supplier-site information for VMI (Vendor Managed Inventory) scenarios, and constructing kanban detail records. The package does not stand alone — it collaborates directly with INV_KANBAN_PVT, INV_KANBANCARD_PKG, and FLM_KANBAN_CUSTOM_PKG, and it references FND_API, FND_GLOBAL, FND_PROFILE, and INV_LOG_UTIL for standard EBS error handling, session context, profile option lookups, and logging.
Key Procedures and Functions
The ETRM metadata documents seventeen procedures and functions:
- STATUS_CHECK — validates status conditions applicable to kanban processing operations.
- REPLENISHCARD — the principal replenishment routine; drives the action that generates replenishment demand for a kanban card.
- GETLOCATORNAME — returns the descriptive name of a locator from key flexfield information.
- GETORGCODE — resolves the organization code for a given organization.
- GETSUPPLIERSITENAME — retrieves the supplier site name used in sourcing and VMI contexts.
- GETDOCMENTNUMBER — derives document numbers associated with kanban replenishment transactions (for example requisition or PO references).
- GETREPLENISHINFO — assembles replenishment information for display and processing.
- GETSOURCETYPELOV — populates the list of values for replenishment source types.
- GETSUPPLIERLOV — populates the supplier list of values.
- GETSUPPLIERSITELOV — populates the supplier site list of values.
- GETWIPLINELOV — populates the WIP line list of values for discrete work-in-process sourcing.
- GETINQUIRYINFO — gathers inquiry information for the kanban inquiry and workbench screens.
- GET_VMI_VENDOR_SITE_LOV — supplies vendor-site values specific to VMI arrangements.
- GET_VENDOR_LOV — supplies vendor values for selection.
- GET_STARTING_LOT_LOV — supplies starting lot values, used where lot-controlled sourcing applies.
- GET_KANBAN_DETAILS — returns detailed kanban card information.
- GET_KANBAN_MO_DETAILS — returns kanban details specifically tied to manufacturing order context.
Tables Accessed
The package operates against core Inventory, Purchasing, and Work in Process tables through APPS synonyms. Kanban data is read and maintained in MTL_KANBAN_CARDS, MTL_KANBAN_CARD_ACTIVITY, and MTL_KANBAN_PULL_SEQUENCES, with organization defaults from MTL_PARAMETERS. Locator and item data come from MTL_ITEM_LOCATIONS (and its key flexfield view) and MTL_SYSTEM_ITEMS_VL. Replenishment documents are supported by MTL_TXN_REQUEST_HEADERS and MTL_TXN_REQUEST_LINES, with procurement documents in PO_HEADERS_ALL, PO_DISTRIBUTIONS_ALL, PO_REQUISITION_HEADERS_ALL, PO_REQUISITION_LINES_ALL, and PO_VENDORS / PO_VENDOR_SITES_ALL. Work-in-process sourcing uses WIP_ENTITIES and WIP_LINES, while BOM_INVENTORY_COMPONENTS supports component references, and WSM_SOURCE_LOTS_V supplies lot sourcing data. FND_USER, MTL_ITEM_LOCATIONS_KFV, MFG_LOOKUPS, and ORG_ORGANIZATION_DEFINITIONS provide validation and descriptive lookup support.
Usage Notes
INV_KANBAN_PKG is invoked primarily as a supporting layer behind the Oracle Inventory Kanban forms and related concurrent processing. The LOV-provider functions (GETSOURCETYPELOV, GETSUPPLIERLOV, GETSUPPLIERSITELOV, GETWIPLINELOV, GET_VENDOR_LOV, GET_VMI_VENDOR_SITE_LOV, GET_STARTING_LOT_LOV) are characteristic of form-level value-list population, while GETINQUIRYINFO, GET_KANBAN_DETAILS, and GET_KANBAN_MO_DETAILS serve display and inquiry rendering. REPLENISHCARD carries the operational weight for replenishment execution. Because it is classified OTHER and is not referenced by any database object, it should be treated as an internal package: customizations should prefer the associated public APIs in INV_KANBAN_PVT, although direct calls are common in extensions that need the same LOV and inquiry logic. Developers extending kanban functionality should also examine FLM_KANBAN_CUSTOM_PKG, which exists to hold customer-specific kanban logic, and should use FND_API error handling conventions consistent with the rest of the package.
-
PACKAGE: APPS.INV_KANBAN_PKG 12.1.1
-
PACKAGE: APPS.INV_KANBAN_PKG 12.2.2
-
PACKAGE: APPS.INV_KANBAN_PKG 12.2.2
-
PACKAGE: APPS.INV_KANBAN_PKG 12.1.1