Results for “first_article_status”

4 results




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

Overview

MTL_MFG_PART_NUMBERS_ALL_V is an Oracle E-Business Suite (EBS) reporting view owned by the APPS schema and shipped as part of the Inventory (INV) product family. In both release 12.1.1 and 12.2.2 it carries a VALID status and is documented in ETRM with the terse description "10SC ONLY," indicating that its intent is restricted to specific localization or process scopes rather than general-purpose manufacturing use. The view exposes manufacturer part number data that is otherwise distributed across the manufacturer, item, and manufacturing part number tables, joining them into a single denormalized row that is convenient for reporting, extracts, and integration interfaces. Because it is defined as a view rather than a table, it introduces no independent storage and inherits the security, language, and organizational behavior of the tables beneath it.

Underlying Base Objects

The view text joins three base objects, each accessed through SYNONYM references in the APPS schema:

The join predicates are A.MANUFACTURER_ID = B.MANUFACTURER_ID and A.INVENTORY_ITEM_ID = IT.INVENTORY_ITEM_ID combined with A.ORGANIZATION_ID = IT.ORGANIZATION_ID. The ROW_ID column is derived from A.ROWID, giving consumers a stable pointer back to the underlying manufacturing part number row. The language predicate means the view is session-language sensitive and returns item descriptions in the caller's current EBS language.

Key Columns

The column list reflects the three-object join and includes the following categories:

FIRST_ARTICLE_STATUS and APPROVAL_STATUS are the columns most closely tied to the view's stated purpose; they track the first-article and approval lifecycle of a manufacturer part number and are the fields typically queried when validating part readiness.

Common Use Cases and Queries

The view is used to report manufacturer part numbers in the context of an inventory item, for example to produce approved-source lists, first-article tracking reports, or integration extracts that require the item description in the user's language.

  • Approved part numbers for an item: SELECT mfg_part_num, manufacturer_name, first_article_status, approval_status FROM mtl_mfg_part_numbers_all_v WHERE inventory_item_id = :item_id AND organization_id = :org_id.
  • Pending first-article review: SELECT mfg_part_num, manufacturer_name FROM mtl_mfg_part_numbers_all_v WHERE first_article_status = :status_code.
  • Audit extract: SELECT row_id, inventory_item_id, mfg_part_num, creation_date, last_update_date FROM mtl_mfg_part_numbers_all_v WHERE last_update_date >= :since.

Because the underlying data is organization-specific and language-sensitive, queries should always constrain ORGANIZATION_ID where applicable and be aware that ITEM_DESCRIPTION depends on USERENV('LANG'). Given the "10SC ONLY" designation, implementers should verify with functional owners that this view is within the intended scope before reusing it in custom code or interfaces.