Search Results boolean_data

Overview

GMD_TECHNICAL_DATA_VL is an APPS-owned view within the Process Manufacturing Product Development (GMD) module of Oracle E-Business Suite, documented and VALID in both releases 12.1.1 and 12.2.2. It presents technical data records associated with process manufacturing items, lots, formulas, and batches. The view joins header and detail technical data into a single, denormalized result set, and exposes the individual technical parameter that each detail row represents. It is the principal reporting and integration surface for parameterized technical specifications held against manufacturing entities, and it is the object that surfaces the BOOLEAN_DATA column — the attribute most commonly sought by users searching on that term.

Because the "_VL" suffix conventionally denotes a validated or user-facing view rather than a base table, GMD_TECHNICAL_DATA_VL is intended as a read-only interface. It is not a storage object; no inserts, updates, or deletes should be issued against it. Its presence in the APPS schema also means it participates in the standard EBS security model, so any custom reporting must observe the appropriate organization and responsibility access controls.

Underlying Base Objects

The ETRM metadata documents the following referenced base objects, all accessed through synonyms in the APPS schema:

• GMD_TECHNICAL_DATA_HDR (aliased H) — the header table holding the identifying context: technical data identifier, organization code, item, lot, formula, and batch references.
• GMD_TECHNICAL_DATA_DTL (aliased D) — the detail table storing the actual parameter values, together with audit columns and the sort sequence.
• GMD_TECH_PARAMETERS_B (aliased B) — the technical parameter definition table supplying the parameter identifier and its display name.

H and D are joined on TECH_DATA_ID, and D and B are joined on TECH_PARM_ID. The view additionally filters on H.DELETE_MARK = 0, so logically deleted technical data headers are excluded from all results. The driving relationship is therefore one header to many details, with each detail enriched by its parameter definition.

Key Columns

• TECH_DATA_ID — primary identifier of the technical data header; the join key to the detail rows.
• ITEM_ID, LOT_ID, FORMULA_ID, BATCH_ID — the process manufacturing entity to which the technical data applies.
• INVENTORY_ITEM_ID, ORGANIZATION_ID, LOT_ORGANIZATION_ID, ORGN_CODE, LOT_NUMBER — inventory-facing identifiers that allow the view to be linked directly to item and lot master data.
• TECH_PARM_ID, TECH_PARM_NAME — the technical parameter being recorded and its human-readable name.
• SORT_SEQ — ordering sequence used to present parameters in a defined display order.
• TEXT_DATA, NUM_DATA, BOOLEAN_DATA, TEXT_CODE — the value columns. Only one is typically populated per row, according to the parameter's data type; BOOLEAN_DATA holds yes/no style parameter values.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — audit columns inherited from the detail table.
• DELETE_MARK — always zero in returned rows, since the view filters on it.

Common Use Cases and Queries

Typical uses include technical specification reports for a formula or batch, quality and compliance extracts listing boolean parameter settings, and integration feeds that export parameter values to external systems. Because BOOLEAN_DATA drives the majority of searches against this object, it is usually filtered or selected explicitly.

Example — all boolean technical parameters for a given item:

• SELECT tech_parm_name, boolean_data, text_data, num_data, lot_number
FROM apps.gmd_technical_data_vl
WHERE inventory_item_id = :item_id
AND boolean_data IS NOT NULL
ORDER BY sort_seq;

Example — parameter values for a specific formula, with audit context:

• SELECT tech_parm_name, text_data, num_data, boolean_data, text_code,
      last_updated_by, last_update_date
FROM apps.gmd_technical_data_vl
WHERE formula_id = :formula_id
ORDER BY sort_seq;

When joining to inventory, link on INVENTORY_ITEM_ID and ORGANIZATION_ID to obtain item descriptions, or on LOT_ID for lot attributes. Always constrain by organization where multiple operating units are in scope, and avoid applying any DML against this object.