Results for “fa_inv_interface_v”

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

Overview

FA_INV_INTERFACE_V is a retrofitted Oracle E-Business Suite view owned by the APPS schema in the Oracle Assets (OFA) product. It exposes the contents of the FA_INV_INTERFACE staging table in a denormalized, reporting-friendly form by resolving foreign keys into their descriptive values and by pivoting the flexfield segment columns of the location, category, and asset key flexfields into discrete columns. The view is a read-only query construct; the FA_INV_INTERFACE table itself is the interface used to load physical inventory reconciliation data into Oracle Assets, typically from feeder systems or from the Oracle Inventory physical inventory process.

Because the view carries translated lookup meanings and key flexfield segment values, it is suited to operational reporting, reconciliation review, and downstream integrations that need human-readable inventory interface data without performing their own joins to FA_LOOKUPS, FA_LOCATIONS, FA_CATEGORIES, and FA_ASSET_KEYWORDS. In 12.1.1 and 12.2.2 the object is documented as VALID and is defined in the standard APPS schema, so it is queried as APPS.FA_INV_INTERFACE_V.

Underlying Base Objects

ETRM metadata for 12.2.2 documents the following referenced base objects, all accessed through APPS synonyms: FA_INV_INTERFACE, FA_DISTRIBUTION_HISTORY, FA_LOOKUPS, FA_CATEGORIES, FA_LOCATIONS, and FA_ASSET_KEYWORDS. The view text confirms these same tables plus three aliased instances of FA_LOOKUPS (LU, LU2, LU3) used to translate status and reconciliation method codes.

• FA_INV_INTERFACE (ITF) is the driving table and supplies the primary interface data.
• FA_DISTRIBUTION_HISTORY (DH) is outer-joined on ASSET_ID and DISTRIBUTION_ID (+).
• FA_LOOKUPS is outer-joined three times: LOOKUP_TYPE 'INVENTORY STATUS', LOOKUP_TYPE LIKE 'INVENTORY UNIT METHOD%', and LOOKUP_TYPE LIKE 'INVENTORY LOCATION METHOD%'.
• FA_CATEGORIES (CAT) is outer-joined on ASSET_CATEGORY_ID = CATEGORY_ID, providing seven category key flexfield segments.
• FA_LOCATIONS (LOC) is outer-joined on LOCATION_ID, providing seven location key flexfield segments.
• FA_ASSET_KEYWORDS (KEY) is outer-joined on ASSET_KEY_CCID = CODE_COMBINATION_ID, providing nine asset key segments.

All joins are outer joins, so an interface row is returned even when the distribution, lookup, category, location, or asset key record is missing.

Key Columns

• INVENTORY_NAME, INVENTORY_ID — identifying information for the physical inventory being reconciled.
• ASSET_ID, ASSET_NUMBER, TAG_NUMBER, DESCRIPTION, MODEL_NUMBER, SERIAL_NUMBER, MANUFACTURER_NAME, UNITS — descriptive asset attributes carried on the interface row.
• STATUS — translated meaning of the FA_LOOKUPS code with LOOKUP_TYPE 'INVENTORY STATUS'.
• UNIT_RECONCILE_MTH, LOC_RECONCILE_MTH — translated meanings of the unit and location reconciliation methods.
• DISTRIBUTION_ID, RECONCILIATION_ID — identifiers linking the row to distribution history and the reconciliation run.
• LOC_SEGMENT1..LOC_SEGMENT7 — the location key flexfield segments sourced from FA_LOCATIONS.SEGMENTn and aliased LOC_SEGMENTn. LOC_SEGMENT1 is the location segment most commonly searched by users.
• CAT_SEGMENT1..CAT_SEGMENT7 — category key flexfield segments from FA_CATEGORIES.
• KEY_SEGMENT1..KEY_SEGMENT9 — asset key flexfield segments from FA_ASSET_KEYWORDS.

Common Use Cases and Queries

Typical uses include reviewing interface rows pending transfer to Oracle Assets, validating that location and category flexfield values were populated correctly, and building reconciliation exception reports. A common search pattern targets the location segment, for example:

SELECT inventory_name, asset_number, tag_number, status, loc_segment1, loc_segment2, loc_segment3 FROM apps.fa_inv_interface_v WHERE loc_segment1 = :p_location_company ORDER BY inventory_name, asset_number;

To list all locations appearing in the interface with their translated reconciliation methods:

SELECT DISTINCT loc_segment1, loc_segment2, loc_reconcile_mth FROM apps.fa_inv_interface_v ORDER BY loc_segment1, loc_segment2;

To find rows whose asset key or category could not be resolved (outer-join misses):

SELECT asset_id, asset_number, cat_segment1, key_segment1 FROM apps.fa_inv_interface_v WHERE cat_segment1 IS NULL OR key_segment1 IS NULL;

Because the view is read-only and defined in APPS, queries should use fully qualified names and appropriate access grants; data changes must be made against FA_INV_INTERFACE directly rather than through the view.