Results for “kanban_size”

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

Overview

INVBV_KANBAN_CARDS is a read-only Oracle EBS view owned by the APPS schema and registered under the INV (Inventory) product module. It presents data from the Kanban card infrastructure of Oracle Inventory, exposing the attributes of records held in the MTL_KANBAN_CARDS base table. Within Oracle EBS 12.1.1 and 12.2.2, Kanban cards represent replenishment signals used in pull-based manufacturing and supply execution, where a card authorizes the movement, production, or procurement of material once a trigger point is reached. The view provides a reporting and integration surface over that operational data, allowing forms, concurrent programs, OBIEE extracts, and custom interfaces to read Kanban card details without querying the base table directly.

The view is documented as "Retrofitted" in the ETRM reference material, indicating that it was adapted to align with the current view architecture where translation and security logic are handled through column-level expression directives rather than inline joins. Its status is VALID, confirming that the underlying definition compiles successfully against the referenced base object in the supported releases.

Underlying Base Objects

INVBV_KANBAN_CARDS is defined over a single documented base object: MTL_KANBAN_CARDS, accessed through the APPS synonym MTL_KANBAN_CARDS. There are no additional tables, joins, or outer queries referenced in the documented definition. This direct dependency means the view is a straightforward projection of the base table, with the most significant transformation being the substitution of stored lookup codes with translated meanings and the imposition of organization-level security.

The view text applies a WHERE clause of the form '_SEC:MKC.ORGANIZATION_ID' IS NOT NULL, which enforces the EBS security model. This directive restricts the rows returned according to the organization access privileges of the session, ensuring that users only see Kanban cards belonging to inventory organizations they are authorized to query. The view is further declared WITH READ ONLY, so no DML may be issued against it; all maintenance of Kanban cards must occur through the base table and the standard Inventory application forms.

Key Columns

The view exposes the full set of business-relevant attributes of a Kanban card. Principal identifiers include KANBAN_CARD_ID, the primary key, and KANBAN_CARD_NUMBER, the user-visible card number. PULL_SEQUENCE_ID links the card to the pull sequence that governs its replenishment logic, while INVENTORY_ITEM_ID and ORGANIZATION_ID identify the item and the inventory organization in which the card operates. SUBINVENTORY_NAME and INVENTORY_LOCATOR_ID pinpoint the supply or storage location.

Several columns are exposed through lookup directives against the MFG_LOOKUPS table, presented in the view with aliases such as "_LA:SUPPLY_STATUS", "_LA:CARD_STATUS", "_LA:KANBAN_CARD_TYPE", "_LA:SOURCE_TYPE", and "_LA:ERROR_CODE". These return the translated MEANING values for the corresponding MTL_KANBAN_* lookup types, so report consumers receive descriptive text rather than raw codes. KANBAN_SIZE carries the replenishment quantity. Supplier sourcing is represented by SUPPLIER_ID and SUPPLIER_SITE_ID, while internal sourcing uses SOURCE_ORGANIZATION_ID, SOURCE_SUBINVENTORY_NAME, and SOURCE_INVENTORY_LOCATOR_ID. The columns LAST_PRINT_DATE, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and WIP_LINE_ID support audit tracking and work-in-process linkage.

Note that the column listing in the ETRM metadata uses short aliases (for example, "_LA:SUPPLY_STATUS") corresponding to the full expression directives in the view text.

Common Use Cases and Queries

Typical uses include Kanban card status reporting, replenishment exception analysis, and integration extracts feeding supplier collaboration or shop-floor systems. A basic query retrieves active cards for an organization:

• SELECT kanban_card_number, inventory_item_id, card_status, supply_status, kanban_size FROM apps.invbv_kanban_cards WHERE organization_id = :org_id;
• SELECT kanban_card_number, supplier_id, supplier_site_id FROM apps.invbv_kanban_cards WHERE source_type = 'SUPPLIER';
• SELECT kanban_card_number, error_code, last_print_date FROM apps.invbv_kanban_cards WHERE error_code IS NOT NULL;

Because the view enforces organization security and resolves lookups automatically, it is well suited to ad hoc reporting and to custom concurrent programs that must respect the same access model as the standard Inventory forms. The view name itself is associated with Kanban card data originally encountered in Japanese-language search contexts, reflecting the term used for Kanban-style replenishment cards in Japanese manufacturing environments.