Results for “active_date”

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

Overview

INVFV_SHIP_METHODS is an Oracle EBS 12.1.1 and 12.2.2 view owned by the APPS schema and registered under the Inventory (INV) product family. Its documented description is simply "Retrofitted," which indicates that the object was migrated into the current EBS data model to preserve backward compatibility with an earlier interface while continuing to expose ship method reference data to downstream forms, reports, and integrations. Functionally, the view presents a filtered, read-only list of shipping method values for use wherever a ship method code or description must be displayed or validated.

The view is defined with a WITH READ ONLY clause, so it can be queried but never used as a DML target. Applications, concurrent programs, and custom reports that require the set of active or historical ship methods can select from INVFV_SHIP_METHODS rather than querying the underlying lookup structures directly, giving a stable, appearance-specific interface to that reference data.

Underlying Base Objects

Per the ETRM 12.2.2 metadata, the view is defined over two documented base objects:

• FND_COMMON_LOOKUPS (VIEW) — supplies the actual ship method rows. The view filters this source by APPLICATION_ID = 401 (Oracle Inventory) and LOOKUP_TYPE = 'SHIP_METHOD', ensuring only Inventory shipping method lookups are returned.
• FND_GLOBAL (PACKAGE) — the standard EBS session context package, used for environment and responsibility context within the view's definition and any dependent logic.

Because the source is itself the FND_COMMON_LOOKUPS view (rather than the FND_LOOKUPS base table), INVFV_SHIP_METHODS is a view layered over another view. This is consistent with the "Retrofitted" designation: the object bridges legacy code paths that expect a dedicated ship methods view with the consolidated Oracle Application Object Library lookup repository.

Key Columns

• SHIP_METHOD_CODE — the lookup code value, aliased from FCL.LOOKUP_CODE, serving as the unique ship method identifier used throughout order and shipping transactions.
• SHIP_METHOD — the user-facing name of the ship method, derived from FCL.MEANING.
• DESCRIPTION — additional free-text detail from FCL.DESCRIPTION.
• "_LA:INACTIVE_FLAG" — a special attribute (the quoted column reflecting the _LA:FCL.ENABLED_FLAG:FND_LOOKUPS:YES_NO:MEANING descriptor) that surfaces the lookup's enabled/disabled state via the FND_LOOKUPS YES_NO meaning, identifying inactive ship methods.
• ACTIVE_DATE — the START_DATE_ACTIVE from the lookup, marking when the ship method becomes valid.
• INACTIVE_DATE — the END_DATE_ACTIVE, marking when the ship method expires or is retired.

Common Use Cases and Queries

Typical scenarios include populating ship method lists of values on order management and shipping forms, validating ship method codes during integration, and reporting on the currently valid set of shipping methods. Because the view is read-only, it is safe to reference in custom concurrent programs and BI Publisher data models.

• List all ship methods: SELECT ship_method_code, ship_method FROM invfv_ship_methods;
• Retrieve only currently active methods: SELECT ship_method_code, ship_method FROM invfv_ship_methods WHERE active_date <= SYSDATE AND (inactive_date IS NULL OR inactive_date >= SYSDATE);
• Join to order/shipping data: SELECT o.order_number, s.ship_method FROM oe_order_headers_all o, invfv_ship_methods s WHERE o.ship_method_code = s.ship_method_code;

Analysts should note that the effective set of rows depends entirely on the FND_COMMON_LOOKUPS entries for APPLICATION_ID 401 and LOOKUP_TYPE 'SHIP_METHOD', so any addition, disablement, or date change made in the Inventory lookup maintenance screens is immediately reflected in this view.