Search Results active_date

Overview

INVBV_SHIP_METHODS is a read-only view owned by the APPS schema in Oracle E-Business Suite, registered under the Inventory (INV) product module. It presents a business-friendly, filtered projection of shipping method values maintained in the Oracle Applications common lookup infrastructure. The view is classified in the ETRM repository as valid and is annotated as "Retrofitted," indicating that it was introduced or adapted to preserve backward compatibility with an earlier object interface, most commonly for reporting, concurrent programs, or custom integrations that previously referenced a base-table-level ship method source.

Functionally, the view exposes the set of shipping methods defined for the Inventory application by filtering FND_COMMON_LOOKUPS on APPLICATION_ID = 401 (the Inventory application) and LOOKUP_TYPE = 'SHIP_METHOD'. It therefore acts as a controlled dictionary of valid shipping methods available to order entry, shipping, and fulfillment transactions. Its read-only definition (WITH READ ONLY) enforces that consumers treat the shipping method list as reference data maintained through the standard lookup maintenance forms rather than through direct DML.

Underlying Base Objects

The documented base objects are FND_COMMON_LOOKUPS, itself a view in the APPS schema, and the FND_GLOBAL package. The core data source is FND_COMMON_LOOKUPS, which stores lookup codes, their meanings, descriptions, effective date ranges, enabled flags, and the application and lookup type to which each code belongs. INVBV_SHIP_METHODS restricts this set to Inventory (APPLICATION_ID = 401) and the SHIP_METHOD lookup type.

FND_GLOBAL is referenced in the canonical form of such lookup views, typically to resolve the current application, responsibility, or session context used in enabled-flag and security filtering. Where FND_GLOBAL is invoked, its role is to supply runtime context rather than persistent data. As a view over another view, INVBV_SHIP_METHODS inherits the underlying base table structure of the common lookups model and does not maintain its own storage.

Key Columns

• SHIP_METHOD_CODE — the lookup code from FND_COMMON_LOOKUPS.LOOKUP_CODE; the internal value stored on shipping and order records.
• SHIP_METHOD — the display meaning of the shipping method, from FND_COMMON_LOOKUPS.MEANING.
• DESCRIPTION — the descriptive text associated with the shipping method.
• _LA:INACTIVE_FLAG — a descriptive-flexfield style attribute derived from FCL.ENABLED_FLAG using the YES_NO lookup type and the MEANING value, used to indicate whether the shipping method is currently enabled.
• ACTIVE_DATE — the start date of the shipping method's effective range, mapped from FCL.START_DATE_ACTIVE.
• INACTIVE_DATE — the end date of the effective range, mapped from FCL.END_DATE_ACTIVE.

Common Use Cases and Queries

The most frequent use is populating shipping method lists of values in reports, custom forms, and integration payloads, and validating that a ship method supplied by an external system is still active. The following query returns only currently effective shipping methods, which is the typical pattern triggered by a search on "active_date":

SELECT ship_method_code, ship_method, description, active_date, inactive_date
FROM apps.invbv_ship_methods
WHERE TRUNC(SYSDATE) BETWEEN NVL(active_date, TRUNC(SYSDATE))
AND NVL(inactive_date, TRUNC(SYSDATE))
ORDER BY ship_method;

For reporting historical accuracy, consumers should avoid applying the active_date filter and instead expose the full list with dates, allowing the report to evaluate validity as of the transaction date. Because the view is read-only and derives all content from common lookups, changes to shipping methods must be made through the lookup maintenance interface, not through this view.