Results for “engineering_date”

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

Overview

MTL_SYSTEM_ITEMS_FKEYS_V is an APPS-owned view in the INV – Inventory product, exposed in Oracle EBS 12.1.1 and 12.2.2. Its documented description is limited to the notation "10SC ONLY," indicating that the object was built for a specific Oracle internal or specialized configuration (10SC) rather than for general-purpose reporting. Despite this restricted designation, the view is registered as VALID in the EBS data dictionary and remains referenceable by any session with privileges on APPS objects.

Functionally, the view presents a flattened, denormalized projection of a single inventory item as defined in MTL_SYSTEM_ITEMS_B, enriched with the surrounding attribute context an item carries in Oracle Inventory: organization and master-organization relationships, buyer and planner identities, hazard and UN classifications, receiving routing, ATP and picking rules, return and terms references, coverage templates, and a long list of coded attributes resolved to their display meanings. Because it pre-joins and pre-decodes these attributes, the view serves as a convenient integration and reporting surface where consumers need item-level descriptive context without reconstructing dozens of lookup joins manually.

Underlying Base Objects

The view is defined over a large join set. The driving table is MTL_SYSTEM_ITEMS_B (referenced as a synonym), joined to MTL_PARAMETERS to obtain the master organization identifier. Master-organization comparison is performed inline through a DECODE expression that returns 0 when the item's organization equals the master organization and 1 otherwise.

• Organizational context: HR_ORGANIZATION_UNITS (ORG1, ORG2) and the item's own organization code/master organization.
• Personnel: PER_PEOPLE_F, with name formatting supplied by the HR_PERSON_NAME, HR_GENERAL, and HR_SECURITY packages.
• Compliance and logistics: PO_HAZARD_CLASSES, PO_UN_NUMBERS, RCV_ROUTING_HEADERS.
• Rules and terms: MTL_ATP_RULES, MTL_PICKING_RULES, RA_RULES (twice), RA_TERMS.
• Lookups: PO_LOOKUP_CODES (PO1–PO4), FND_COMMON_LOOKUPS (FND, FND2, FND3, FND4), FND_LOOKUPS (FND1), CS_LOOKUPS (CSL), and numerous MFG_LOOKUPS aliases (MFG1–MFG24) that resolve coded item attributes to their meanings.
• Coverage: OKS_COVERAGE_TEMPLTS_V.

The heavy dependence on lookup views such as FND_COMMON_LOOKUPS, MFG_LOOKUPS, and CS_LOOKUPS is directly relevant to the "lookup_code" search that surfaced this object: the view converts stored lookup codes into human-readable MEANING values.

Key Columns

• INVENTORY_ITEM_ID, ORGANIZATION_ID — the primary item/organization key.
• ORGANIZATION_CODE, MASTER_ORGANIZATION_ID — organizational identification; the unnamed DECODE column flags master-organization membership.
• FULL_NAME — buyer/planner name from PER_PEOPLE_F.
• Hazard attributes: HAZARD_CLASS, UN_NUMBER.
• Routing, ATP, and picking context: ROUTING_NAME, RULE_NAME, PICKING_RULE_NAME.
• Multiple MEANING columns sourced from FND_COMMON_LOOKUPS, FND_LOOKUPS, MFG_LOOKUPS, and CS_LOOKUPS — these expose the decoded values behind lookup codes.
• DISPLAYED_FIELD columns from PO_LOOKUP_CODES.
• ENGINEERING_DATE, TERM.NAME, and OKS coverage NAME.

Common Use Cases and Queries

The view is most useful when reporting needs item context alongside decoded lookup meanings, and when the "10SC" restriction aligns with the deployment. Typical usage:

• Resolving item attributes to readable meanings for extracts or interfaces.
• Confirming master-organization membership for an item.
• Extracting hazard class, UN number, ATP rule, and picking rule for logistics reporting.

Sample query joining to a lookup by code:

SELECT INVENTORY_ITEM_ID, ORGANIZATION_ID, ORGANIZATION_CODE, HAZARD_CLASS, UN_NUMBER, RULE_NAME, PICKING_RULE_NAME FROM APPS.MTL_SYSTEM_ITEMS_FKEYS_V WHERE INVENTORY_ITEM_ID = :item_id AND ORGANIZATION_ID = :org_id;

Because the underlying lookups carry LOOKUP_CODE and MEANING columns, consumers filtering on "lookup_code" should query FND_COMMON_LOOKUPS, MFG_LOOKUPS, or CS_LOOKUPS directly for code-level filtering, and use this view to obtain the already-decoded MEANING values for the item record.