Results for “document_detail_id”

31 results




Overview
Explore in AI Chat

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

Overview

INVBV_KANBAN_CARD_ACTIVITIES is a read-only view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Inventory (INV) product family. It is a "B" (base/backing) view, denoted by the "BV" naming convention, and presents kanban replenishment activity data for reporting and integration purposes. The view is documented in ETRM 12.2.2 as "Retrofitted," indicating it was added or recreated to support a specific functional requirement, typically layered security and lookup translation applied on top of an underlying transactional table. In EBS 12.1.1 and 12.2.2, this view surfaces a denormalized, presentation-ready projection of kanban card activity, with organization-level security enforced and several coded columns resolved to their display meanings. It is primarily consumed by Oracle Inventory forms, concurrent programs, and external integrations that need to query kanban activity without directly touching the base transaction table.

Underlying Base Objects

The view is defined over a single base object, MTL_KANBAN_CARD_ACTIVITY, referenced through a synonym (MTL_KANBAN_CARD_ACTIVITY). The view text aliases this table as MKA and selects its columns with no joins, making the view a straightforward projection with three notable behavioral characteristics. First, a WHERE clause of '_SEC:MKA.ORGANIZATION_ID' IS NOT NULL applies Multi-Org / MOAC security, restricting rows by the operating unit or organization context of the querying session. Second, several lookup columns are exposed using _LA (lookup attribute) aliases, which instruct the Oracle Forms / OA Framework translation layer to resolve codes against MFG_LOOKUPS. Third, the view is declared WITH READ ONLY, so no DML is permitted. Because the view references the base table directly, it inherits all organization partitioning and indexing of MTL_KANBAN_CARD_ACTIVITY.

Key Columns

Common Use Cases and Queries

Typical uses include querying kanban activity for a specific organization, tracking card supply and status history, and feeding replenishment data into custom reports. The _LA aliases are meaningful to the OA Framework layer; direct SQL against the view returns the raw code values for those columns, so reports must join MFG_LOOKUPS explicitly for meanings.

Example: retrieve recent activity for an item and organization.

SELECT kanban_card_number,
       subinventory_name,
       kanban_size,
       last_update_date
FROM   apps.invbv_kanban_card_activities
WHERE  organization_id = :org_id
AND    inventory_item_id = :item_id
ORDER BY last_update_date DESC;

Example: summarize activity by card status.

SELECT card_status, COUNT(*)
FROM   apps.invbv_kanban_card_activities
WHERE  organization_id = :org_id
GROUP BY card_status;

Because of the MOAC predicate, queries must run with a valid organization context, and callers should treat the view as strictly read-only.