Search Results qa_inspection_point

Overview

APPS.EDW_LOOKUP_CODE_FKV is a flattened key-value view used by the Oracle E-Business Suite Enterprise Data Warehouse (EDW) and Oracle Business Intelligence Applications (OBIA) extraction layer. Its purpose is to expose QuickCode / lookup code values from multiple Oracle EBS schemas through a single, uniform interface so that downstream ETL processes can materialize lookup dimension data without issuing source-specific queries. The view is part of the "FKV" (Flattened Key Value) family of objects that present resolved lookup meanings and codes in a form suitable for warehouse staging.

In EBS 12.1.1 and 12.2.2 the view is defined over FND_LOOKUP_VALUES and a second source, CM_MTHD_MS. It normalizes lookup data from the Manufacturing (MFG), Purchasing/Order Management (PO), and Process Manufacturing (OPM) product families, which in their native form are distinguished by VIEW_APPLICATION_ID and lookup types. The view is therefore primarily a reporting and integration object rather than a transactional one.

Underlying Base Objects

The documented definition is a UNION ALL of four branches:

• PO branch — selects from FND_LOOKUP_VALUES where VIEW_APPLICATION_ID = 201, SECURITY_GROUP_ID = 0, and LANGUAGE = USERENV('LANG'), restricted to lookup types such as RCV TRANSACTION TYPE, INSPECTION STATUS, PRICE TYPE, DOCUMENT STATE, DESTINATION TYPE, ORDER TYPE, SHIPMENT TYPE, FREIGHT TERMS, FOB, and PURCHASE CLASSIFICATION.
• MFG branch — selects from FND_LOOKUP_VALUES where VIEW_APPLICATION_ID = 700, covering lookup types such as MRP_ORDER_TYPE, WIP_DISCRETE_JOB, WIP_JOB_STATUS, MTL_PLANNING_MAKE_BUY, MTL_LOT_CONTROL, MTL_SERIAL_CONTROL, and WIP_ENTITY.
• QA branch — selects the QA_INSPECTION_POINT lookup type where VIEW_APPLICATION_ID = 3.
• OPM branch — selects cost_mthd_code from CM_MTHD_MS, tagged with the synthetic lookup type OPI_OPM_COST_METHOD.

No additional base objects are documented in the ETRM 12.2.2 metadata; the view is dependent entirely on these two physical tables plus the EBS session environment function USERENV.

Key Columns

• LOOKUP_CODE_PK — a concatenated surrogate key of the form UPPER(lookup_code) || '-' || UPPER(lookup_type) || '-' || table_code. It uniquely identifies each row across the unioned sources and is used as the join key in the EDW star schema.
• LOOKUP_TYPE — the QuickCode lookup type (for example, ORDER TYPE or WIP_JOB_STATUS), or the synthesized value OPI_OPM_COST_METHOD for the OPM branch.
• LOOKUP_CODE — the stored code value. For the OPM branch this maps to the column cost_mthd_code.
• TABLE_CODE — the source-family discriminator, taking the literal values PO, MFG, or OPM.

Common Use Cases and Queries

The view is typically queried by ETL routines or ad-hoc reporting to resolve lookup codes into a single consistent dimension. A representative query retrieves all codes for a given lookup type:

SELECT lookup_code_pk, lookup_type, lookup_code, table_code FROM apps.edw_lookup_code_fkv WHERE lookup_type = 'ORDER TYPE' ORDER BY lookup_code;

A second common pattern restricts results to a single source family, which is useful when validating extract completeness:

SELECT lookup_type, COUNT(*) FROM apps.edw_lookup_code_fkv WHERE table_code = 'MFG' GROUP BY lookup_type ORDER BY lookup_type;

Because the definition filters on USERENV('LANG'), callers must be aware that results are language-dependent and that a session language with no translated rows will return an empty set for the corresponding lookup types. The security group constraint of zero further limits output to global, non-secured lookup values.