Results for “safety_stock_days”

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

Overview

The view APPS.INVBV_KANBAN_LOCATION_ITEMS is an Inventory (INV) module database object shipped in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes kanban pull sequence definitions that are maintained at the item and location level, presenting the data in a form intended for reporting, inquiry, and integration rather than for transactional processing. The object is documented as "Retrofitted," indicating that it was introduced or reshaped during an upgrade or a code retrofit cycle to support existing forms and reports in the INV schema.

The principal characteristic of this view is its restrictive filter: it returns only rows where KANBAN_PLAN_ID = -1. In the kanban model, the value -1 designates the "location items" context — that is, item and subinventory level kanban definitions rather than rows governed by a named kanban plan. The view also carries Oracle Forms descriptive headers, such as _LA:MKP.SOURCE_TYPE and _LA:MKP.CALCULATE_KANBAN_FLAG, which are metadata artifacts used by the Forms engine to resolve lookup meanings and column labels. The view includes neither a kanban plan identifier nor any plan-level attributes, so it functions as a location-centric projection of the underlying pull sequence data.

Underlying Base Objects

The view is defined over a single documented base object, MTL_KANBAN_PULL_SEQUENCES, referenced through a synonym in the APPS schema. Every column exposed by the view is drawn from that table, aliased in the definition as MKP. The filter MKP.KANBAN_PLAN_ID = -1 isolates the location item records, and the view is declared WITH READ ONLY, so no DML may be performed against it through the view.

A second predicate, expressed as _SEC:MKP.ORGANIZATION_ID IS NOT NULL, is a server-side security token processed by the Oracle Applications framework. It restricts returned rows to organizations to which the querying responsibility has access. This security construct, together with the descriptive _LA: lookup columns, marks the view as a Forms-oriented object; direct SQL access by non-privileged users will not resolve these tokens in the same way the Forms runtime does.

Key Columns

• PULL_SEQUENCE_ID — Primary identifier of the kanban pull sequence record.
• INVENTORY_ITEM_ID, ORGANIZATION_ID, SUBINVENTORY_NAME, INVENTORY_LOCATOR_ID — The item and stocking location for which the kanban is defined.
• SAFETY_STOCK_DAYS — Safety stock expressed in days of demand, used to size the kanban buffer above expected replenishment lead time.
• SOURCE_TYPE — Lookup-driven value identifying the supply source, such as supplier, inter-org transfer, or WIP.
• SUPPLIER_ID, SUPPLIER_SITE_ID, SOURCE_ORGANIZATION_ID, SOURCE_SUBINVENTORY_NAME, SOURCE_INVENTORY_LOCATOR_ID, WIP_LINE_ID — Source attributes corresponding to the chosen source type.
• REPLENISHMENT_LEAD_TIME, KANBAN_SIZE, FIXED_LOT_MULTIPLIER, NUMBER_OF_CARDS, MINIMUM_ORDER_QUANTITY, ALLOCATION_PERCENT — Replenishment and sizing parameters that determine card quantity and order behavior.
• CALCULATE_KANBAN_FLAG — Lookup-driven indicator of whether kanban size is calculated automatically.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard audit columns inherited from the base table.

Common Use Cases and Queries

The view is most useful for reviewing location-level kanban sizing, particularly safety stock in days, and for feeding downstream reporting on replenishment parameters. A query listing kanban definitions for a specific item and organization, including the searched attribute, takes the following form:

• SELECT pull_sequence_id, organization_id, inventory_item_id, subinventory_name, source_type, replenishment_lead_time, safety_stock_days, kanban_size, number_of_cards FROM apps.invbv_kanban_location_items WHERE inventory_item_id = :item_id AND organization_id = :org_id;
• SELECT organization_id, inventory_item_id, safety_stock_days, number_of_cards FROM apps.invbv_kanban_location_items WHERE safety_stock_days > 0 ORDER BY organization_id, inventory_item_id;
• SELECT organization_id, COUNT(*) location_kanban_count FROM apps.invbv_kanban_location_items GROUP BY organization_id;

Because the view is read-only and carries Forms security tokens, it is appropriate for inquiry and extraction. For bulk integration loads or updates to kanban parameters, developers should target MTL_KANBAN_PULL_SEQUENCES directly, respecting organization access and the KANBAN_PLAN_ID = -1 convention for location items.