Search Results check_assy_cfgitem

Overview

MRP_KANBAN_SNAPSHOT_PK is an Oracle EBS application-level PL/SQL package owned by APPS and classified as OTHER in the ETRM metadata for release 12.2.2. It supports the Kanban planning process within Oracle Manufacturing and Supply Chain Management. Its principal responsibility is to identify the set of items that must participate in a given Kanban plan run and to materialize the corresponding bill structures into the working table MRP_KANBAN_LL_CODE for subsequent processing. The package header carries a version constant of '1.0' and declares KANBAN_RELEASE as a NUMBER constant with value 6, indicating a release-phase marker used internally by the Kanban planning logic.

The package is compiled with AUTHID CURRENT_USER, which means its unqualified object references resolve under the privileges of the invoking user rather than as definer-rights code. The $Header directive shows a last committed revision dated 2012/06/27, consistent with the 12.1.1 to 12.2.2 timeframe.

Key Procedures and Functions

The documented API surface comprises five procedures and functions:

• SNAPSHOT_ITEM_LOCATIONS — Returns BOOLEAN. This is the driving entry point that identifies the list of items to be included in the current Kanban plan run. Users may restrict the item set by specifying an item range or an item category. The function selects the bill structure of the qualifying items and inserts the result rows into MRP_KANBAN_LL_CODE.
• ITEM_WHERE_CLAUSE — Returns BOOLEAN and produces, through an output parameter, a dynamically constructed WHERE clause for an item range. The generated predicate is consumed by the first SELECT statement executed during Kanban item snapshotting.
• CATEGORY_WHERE_CLAUSE — Returns BOOLEAN. This is the function matched by the search term "category_where_clause". It builds the WHERE clause for a category range, accepting low and high category bounds plus a table name, and returns the predicate via an output parameter. As with ITEM_WHERE_CLAUSE, the result feeds the initial snapshot SELECT.
• CHECK_MIN_PRIORITY — Returns NUMBER. It evaluates Kanban pull sequence data for a given assembly item, organization, line, and alternate designator to determine minimum priority handling.
• CHECK_ASSY_CFGITEM — Performs configuration item validation for assemblies, complementing the snapshot logic by confirming that candidate assemblies are properly configured.

The dynamic SQL generation pattern (building predicates as strings) explains the inclusion of DBMS_SQL among the referenced objects, since the constructed clauses must be parsed and executed at runtime.

Tables Accessed

The package works against the following documented tables, all reached through APPS synonyms:

• MTL_SYSTEM_ITEMS and MTL_SYSTEM_ITEMS_KFV — the item master and its key-flexfield view, used to resolve item ranges and descriptive attributes.
• MTL_ITEM_CATEGORIES — supplies category assignments required by CATEGORY_WHERE_CLAUSE when restricting the snapshot to a category range.
• MTL_KANBAN_PULL_SEQUENCES — the Kanban pull sequence definitions, read by the priority and snapshot logic.
• MTL_ITEM_LOCATIONS — inventory locators relevant to item-location snapshotting.
• BOM_OPERATIONAL_ROUTINGS and BOM_OPERATION_SEQUENCES — routing and operation sequence data used when traversing bill structure.
• ENG_REVISED_ITEMS — engineering revision information for the selected assemblies.
• MRP_LOW_LEVEL_CODES — low-level coding used to sequence the bill explosion correctly.

Usage Notes

MRP_KANBAN_SNAPSHOT_PK is invoked as part of the Kanban planning cycle, typically from the Kanban calculation or snapshot concurrent program rather than by end users directly. The ETRM metadata records that it is referenced by one other package, indicating that it is called programmatically from a parent Kanban planning package. Custom code should not call the internal WHERE-clause builders directly; the supported invocation point is SNAPSHOT_ITEM_LOCATIONS. Because the package is AUTHID CURRENT_USER and relies on dynamically generated SQL against APPS synonyms, custom callers must execute it under an APPS-enabled session with appropriate MTL and BOM read privileges.