Results for “invbv_future_item_statuses”
20 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
APPS.INVBV_FUTURE_ITEM_STATUSES is a read-only Oracle EBS view in the Inventory (INV) product. It is classified in the ETRM documentation as Retrofitted, meaning it was introduced or regenerated during an upgrade cycle to preserve compatibility with earlier releases and prior interfaces. It presents pending changes to the status of an inventory item within a specific inventory organization.
In EBS, item status controls which transactions, attributes, and functions remain permitted for an item in an organization. A status change is frequently scheduled rather than applied immediately, so a record is held in a pending state until it takes effect. This view exposes those pending item-status rows together with item, organization, and status identifiers, enabling reporting, user-facing inquiry, and integration processes to display future status assignments without querying transactional base tables directly. Because the view is defined WITH READ ONLY, it is not intended for direct DML; status changes are made through supported Inventory forms and APIs.
Underlying Base Objects
Per the documented metadata, INVBV_FUTURE_ITEM_STATUSES accesses four base objects, all reached through synonyms in the APPS schema:
- MTL_PENDING_ITEM_STATUS (PE) — the primary source of pending item-status records; supplies inventory item, organization, status code, effective date, implemented date, and audit columns.
- MTL_SYSTEM_ITEMS (SY) — the item master for the organization; joined on
INVENTORY_ITEM_IDandORGANIZATION_ID. - MTL_PARAMETERS (PA) — organization-level definitions; supplies
ORGANIZATION_CODEand the organization join key. - HR_ALL_ORGANIZATION_UNITS (AL) — provides the organization name (
NAME), joined onORGANIZATION_ID.
The joins bind each pending status row to its item, its owning organization parameters, and the organization unit description, so that rows are returned only for valid item/organization combinations. The view carries a mandatory security predicate on PE.ORGANIZATION_ID, enforcing inventory organization access control at query time.
Key Columns
- ITEM_NAME (
AL.NAMEreference rendered as the item-name key flexfield) — the flexfield description of the item. - ORGANIZATION_NAME — the organization unit name from
HR_ALL_ORGANIZATION_UNITS. - ORGANIZATION_CODE — the 3-character inventory organization code from
MTL_PARAMETERS. - ITEM_STATUS_CODE — the pending item status being applied.
- START_EFFECTIVE_DATE — the date from which the new status is intended to be effective.
- IMPLEMENTED_DATE — the date the pending status was actually carried out. This column is directly relevant to the search term and distinguishes a status that is merely scheduled from one that has been executed. A null implemented date generally indicates the change is still pending.
- STATUS_PENDING_FLAG — a lookup-based indicator (YES/NO meaning) reflecting whether the status is still pending, resolved via the
FND_LOOKUPSYES_NO lookup type. - INVENTORY_ITEM_ID, ORGANIZATION_ID — primary and organization identifiers for joining and filtering.
- LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_DATE, CREATED_BY — audit columns for row-level traceability.
Common Use Cases and Queries
Typical uses include: reporting scheduled versus implemented item-status changes, identifying items whose status change is overdue or still pending, and supporting inventory conversions or data-migration reconciliation.
- Scheduled versus implemented: select rows where
IMPLEMENTED_DATE IS NULLto list statuses that have not yet been executed. - Organization-scoped review: filter by
ORGANIZATION_CODEto review future statuses for a single warehouse. - Audit reporting: order by
LAST_UPDATE_DATEto track recent status maintenance.
A representative query:
SELECT organization_code,
item_name,
item_status_code,
start_effective_date,
implemented_date,
status_pending_flag
FROM apps.invbv_future_item_statuses
WHERE implemented_date IS NULL
ORDER BY organization_code, start_effective_date;
Because the view is read-only and secured by organization, developers should use it strictly as an inquiry and reporting source, directing any status maintenance through supported Inventory functionality.
-
- Retrofitted
APPS.INVBV_FUTURE_ITEM_STATUSES·↳ HR_ALL_ORGANIZATION_UNITS·↳ MTL_PARAMETERS·↳ MTL_PENDING_ITEM_STATUS·Explore INV module →
-
- Retrofitted
APPS.INVBV_FUTURE_ITEM_STATUSES·↳ HR_ALL_ORGANIZATION_UNITS·↳ MTL_PARAMETERS·↳ MTL_PENDING_ITEM_STATUS·Explore INV module →
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
SYNONYM: APPS.MTL_PARAMETERS 12.1.1
-
SYNONYM: APPS.MTL_PARAMETERS 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - INV Tables and Views 12.2.2
-
eTRM - INV Tables and Views 12.1.1
-
eTRM - INV Tables and Views 12.1.1
-
eTRM - INV Tables and Views 12.2.2