Results for “lm_tech_hdr”

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

Overview

LM_TECH_HDR is the technical parameters header table within the Oracle E-Business Suite Process Manufacturing Product Development (GMD) module. It serves as the master definition repository for laboratory technical parameters, storing the header-level attributes that govern how quality and specification parameters are defined for laboratory types. This table is central to the quality management and product development workflow in process manufacturing, where technical parameters define measurable attributes — such as assay values, viscosity, pH, or potency — that must be captured, validated, and tracked across items, formulas, and specifications.

Based on the documented foreign key structure, the table exhibits a hub-leaning data vault classification. This heuristic suggests that LM_TECH_HDR functions as a core reference entity from which multiple dependent (satellite-like) tables branch outward. Its composite primary key, rather than a single surrogate, reinforces its role as a business-keyed master entity rather than a transactional record.

Key Information Stored

The table's structure is intentionally compact. Its primary key is LM_TECH_HDR_PK, composed of two columns:

• LAB_TYPE — The laboratory type identifier. This is the primary organic key of the record, linking each technical parameter to a specific laboratory discipline or testing category. It participates in every foreign key relationship, both inbound and outbound.
• TECH_PARM_NAME — The technical parameter name. Combined with LAB_TYPE, this forms the complete business key. It identifies the specific measurable attribute being defined.
• TEXT_CODE — A foreign key to LM_TEXT_HDR, providing descriptive or instructional text associated with the parameter header (for example, test instructions or handling notes).
• QCASSY_TYP_ID — A foreign key to QC_ASSY_TYP, associating the technical parameter with a quality control assembly type. This supports the linkage between parameter definitions and assembly-level quality structures.

As the composite primary key, LAB_TYPE and TECH_PARM_NAME together uniquely identify each header record; there is no separately documented single-column surrogate key in this metadata. Additional descriptive columns beyond those listed may exist in the physical table, but the documented metadata centers on these key and foreign key attributes.

Common Use Cases and Queries

Typical usage involves resolving the master parameter definitions and tracing them to detail, formula, item, or specification data. Representative query patterns include:

• Listing all technical parameters for a given laboratory type: SELECT TECH_PARM_NAME FROM LM_TECH_HDR WHERE LAB_TYPE = :p_lab_type;
• Joining headers to details: SELECT h.LAB_TYPE, h.TECH_PARM_NAME, d.* FROM LM_TECH_HDR h, LM_TECH_DTL d WHERE h.LAB_TYPE = d.LAB_TYPE AND h.TECH_PARM_NAME = d.TECH_PARM_NAME;
• Retrieving associated descriptive text: SELECT h.*, t.* FROM LM_TECH_HDR h, LM_TEXT_HDR t WHERE h.TEXT_CODE = t.TEXT_CODE;
• Reporting parameter usage across items or specifications by joining LM_ITEM_DAT, LM_FORM_DAT, LM_SPRD_PRM, or LM_SPRD_TEC on LAB_TYPE and TECH_PARM_NAME.

These queries support quality reporting, specification maintenance screens, and integration extracts that feed LIMS or manufacturing execution systems.

Related Objects

LM_TECH_HDR participates in a well-defined web of relationships:

• LM_LTYP_MST — referenced via LAB_TYPE; defines the laboratory type master.
• LM_TEXT_HDR — referenced via TEXT_CODE; supplies descriptive text.
• QC_ASSY_TYP — referenced via QCASSY_TYP_ID; links to QC assembly types.
• LM_TECH_DTL — the detail table, joined on LAB_TYPE and TECH_PARM_NAME.
• LM_FORM_DAT — formula data referencing parameters via LAB_TYPE (and TECH_PARM_NAME).
• LM_ITEM_DAT — item-level parameter data referencing the header.
• LM_SPRD_PRM — spreads parameter data referencing the header.
• LM_SPRD_TEC — spreads technical data referencing the header.

These relationships underscore LM_TECH_HDR's role as the hub from which parameter-level data across items, formulas, spreads, and details is derived.