Search Results get_category_id

Overview

FLM_KANBAN_WORKBENCH_UTIL is a utility package owned by the APPS schema within the Oracle E-Business Suite Flow Manufacturing (FLM) module. Its principal role is to supply shared supporting logic for the Kanban Workbench, the transaction environment in which shop-floor planners, buyers, and production supervisors create, release, and replenish Kanban cards across the supply chain. The package is declared with AUTHID CURRENT_USER, meaning that all unqualified object references resolve against the privileges of the invoking session rather than the package owner. This design lets the Kanban Workbench functionality respect the security profile and organizational access of the individual user executing it, which is consistent with the multi-org, responsibility-driven architecture of EBS 12.1.1 and 12.2.2. Because it is classified as a UTIL package, it is not itself a business transaction endpoint; instead it exposes reusable helper logic consumed by the forms and APIs of the broader Kanban Workbench feature set.

Key Procedures and Functions

The documented interface of FLM_KANBAN_WORKBENCH_UTIL contains a single program unit, GET_CATEGORY_ID. The companion header comment in the source identifies the file as FLMWBUTS.pls and carries the version 115.1.

• GET_CATEGORY_ID — A function that returns a numeric value representing a category identifier. Based on its name and its role as a utility within the Kanban Workbench, it resolves the appropriate item category for a given planning scenario. The function accepts inputs describing the planning context (a plan, an organization, and a component item) and returns the category identifier as a NUMBER. The exact parameter list is documented in the source header and should be verified against the installed version.

No other public procedures or functions are documented in the package specification. A PRAGMA RESTRICT_REFERENCES directive is present, asserting the purity level of the function. This is a legacy PL/SQL construct typical of code originally written in the late 1990s (the header dates to 1999) and retained through later releases for compatibility with SQL call contexts. The purity assertion, combined with the AUTHID CURRENT_USER clause, indicates the function is intended to be safely callable from SQL statements as well as from PL/SQL blocks.

Tables Accessed

The documented table reference for this package is MRP_LOW_LEVEL_CODES, accessed through an APPS synonym. This is a foundational MRP/MPS table that records low-level codes for items, which express how deep an item sits in the product structure and therefore determine the order in which material requirements must be exploded. Within the Kanban context, the low-level code influences plan sequencing and the way component demand is associated with a planning scenario. GET_CATEGORY_ID likely consults the plan and component item inputs against this table to derive the correct category association for the Kanban Workbench. The metadata records only this one table; any additional reads or writes performed internally are not documented in the ETRM excerpt.

Usage Notes

As a utility package, FLM_KANBAN_WORKBENCH_UTIL is not exposed directly to end users through a menu or a scheduled concurrent program. It is invoked indirectly. The documented metadata shows it is referenced by three other packages, indicating that it functions as a shared dependency for higher-level Kanban Workbench logic and possibly for Flow Manufacturing replenishment and planning routines. The Kanban Workbench itself is a Forms-based feature, so calls into this function originate from the form's supporting PL/SQL libraries and package bodies.

Customers extending Flow Manufacturing may also call GET_CATEGORY_ID from custom code that needs to reproduce the standard category resolution logic for a plan, organization, and component combination. Because the package uses AUTHID CURRENT_USER, any custom caller must ensure the invoking schema has the necessary privileges on MRP_LOW_LEVEL_CODES and related APPS synonyms; invoking it from a deliberately restricted session may otherwise fail or return no rows. As with all seeded EBS packages, the specification should be treated as a stable interface while the body remains subject to patching, and any dependency on this utility should be revalidated after application of Flow Manufacturing patches or an upgrade between 12.1.1 and 12.2.2.