Results for “project_number”

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

Overview

QA_FLEX_UTIL is a utility package in the Oracle E-Business Suite Quality (QA) application schema. It is owned by the APPS schema and is classified as a UTIL (utility) API, indicating that it provides shared helper routines rather than a business-facing transaction API. Its principal responsibility is to resolve and format descriptive flexfield and key flexfield attribute values for the Quality module, translating raw identifier columns into human-readable, concatenated display values that can be presented in forms, list of values (LOVs), views, and concurrent program output.

An important characteristic of QA_FLEX_UTIL is its broad dependency footprint. The ETRM metadata records that the package is referenced by 22 other packages and views across the Quality, Inventory, and Order Management domains. Consumers include QA_CRITERIA_V, QA_CRITERIA_V1, QA_RESULTS_V, QA_RESULTS_FULL_V, QA_SPECS_PUB, QA_SAMPLING_PKG, QA_SS_CORE, QA_PLAN_ELEMENT_API, QA_SOLUTION_DISPOSITION_PKG, QA_ERES_UTIL, QA_SKIPLOT_RES_ENGINE, and the QA_SKIPLOT_RCV criteria and results views, among others. This dependency pattern demonstrates that the package functions as a lower-level foundation utility within the QA schema: when flexfield-based specification criteria, sampling rules, or results need to be rendered or validated, the calling object delegates to QA_FLEX_UTIL rather than repeating the lookup logic. On the inbound side, the package depends only on SYS and the STANDARD package, placing it at the bottom of the QA dependency hierarchy.

Key Procedures and Functions

The documented interface exposes 30 procedures and functions. Broadly, they fall into several functional groups.

• Item and locator resolution: ITEM, ITEM2, GET_ITEM_ID, LOCATOR, LOCATOR2, and GET_LOCATOR_ID handle conversion between internal inventory identifiers and their flexfield display representations, using the item and locator key flexfield structures.
• Category resolution: GET_ITEM_CATEGORY_VAL and MTL_CATEGORIES_DESCRIPTION return category values and concatenated category descriptions.
• Source document references: PROJECT_NUMBER, SALES_ORDER, RMA_NUMBER, CONTRACT_NUMBER, CONTRACT_LINE_NUMBER, DELIVERABLE_NUMBER, and WORK_ORDER translate internal foreign keys into the externally recognizable document numbers used in Quality specifications, plans, and collection plans.
• Workflow and project context: GET_PROJECT_ID_FROM_LPN and GET_TASK_ID_FROM_LPN derive project and task identifiers from a license plate number.
• Collection plan support: QPC_RESULT_COLUMN_NAME, QPC_VALUES_EXIST_FLAG, and QCH_PLAN_ID support Quality collection plan character and result handling, including determining whether collection values exist for a given plan.

GET_ITEM_ID and GET_LOCATOR_ID are identifier-returning functions, while ITEM, ITEM2, LOCATOR, and LOCATOR2 are the display-oriented counterparts. No parameter lists are documented in the ETRM record, and callers should consult the package specification in the database for exact signatures.

Tables Accessed

The package reads from several base tables through APPS synonyms. Item and category data are sourced from MTL_SYSTEM_ITEMS_KFV, MTL_ITEM_CATEGORIES, MTL_CATEGORIES_KFV, and MTL_PARAMETERS (which supplies the item key flexfield structure definition). Locator and license plate information comes from WMS_LICENSE_PLATE_NUMBERS and CSI_ITEM_INSTANCES. Source document references are resolved through MTL_SALES_ORDERS, OE_ORDER_HEADERS_ALL, and WIP_ENTITIES for work order context. Quality-specific data is obtained from QA_CRITERIA_HEADERS and QA_PLAN_CHARS. These reads are predominantly descriptive lookups; the package is a utility rather than a transaction API, so write activity against transactional tables is not its primary purpose.

Usage Notes

QA_FLEX_UTIL is not typically invoked directly by end users. It is called from Quality forms and LOVs when specification criteria, sampling criteria, or results must display flexfield-based values, from Quality views such as QA_CRITERIA_V and QA_RESULTS_V, and from concurrent or ERES processes that require formatted item, locator, project, or document references. Because it is referenced by 22 objects, any modification carries a wide blast radius and should be treated as a shared foundation component. Custom code should invoke the package through its documented procedures rather than duplicating the underlying flexfield concatenation logic. The package is documented as VALID in both 12.1.1 and 12.2.2 environments, though its internal dependencies should be verified against the target instance before applying patches.