Results for “lot_status”

50+ results




Overview
Explore in AI Chat

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

Overview

GMD_COMPOSITE_SPEC_DISP is a table in the GMD schema (Process Manufacturing Product Development) within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores display-side records for OPM Quality Composite Specifications, which combine multiple individual specifications into a single quality specification profile applied during disposition decisions. The table links a composite specification to an event specification disposition, defining how a composite quality specification is presented and evaluated for a given disposition event. In this role, it functions as a bridge between the event-level specification disposition logic and the composite specification definition used by quality and product development users.

Under the heuristic Data Vault classification derived from its foreign key structure, the table is modeled as standalone. This suggests it does not participate as a dependent satellite of a parent hub in the mined relationship set; instead, it is best treated as an independent entity keyed by its own composite primary key. Practitioners designing a data vault or reporting layer should therefore model it as its own hub-like object rather than assuming a parent-child satellite relationship.

Key Information Stored

The table contains 12 documented columns. The most significant are:

  • EVENT_SPEC_DISP_ID — Part of the composite primary key and the link to the event specification disposition context.
  • COMPOSITE_SPEC_DISP_ID — The other half of the composite primary key, identifying the composite specification display record.
  • DISPOSITION — Captures the disposition value associated with the composite specification display, used in quality disposition decisions.
  • LOT_STATUS — The lot status applicable to the composite specification display.
  • LATEST_IND — Indicates whether the record is the latest version of the composite specification display.
  • UPDATE_ALL_LOCATIONS_IND — Controls whether the specification update applies across all locations.
  • DELETE_MARK — Soft-delete flag used to logically retire records without physical deletion.
  • CREATION_DATE, CREATED_BY — Standard audit attributes recording when and by whom the record was created.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit attributes recording the most recent update.

The unique index GMD_COMPOSITE_SPEC_DISP_PK (EVENT_SPEC_DISP_ID, COMPOSITE_SPEC_DISP_ID) serves as the business-key candidate and enforces uniqueness of each event/composite specification display pairing.

Common Use Cases and Queries

Typical use cases include quality disposition reporting, composite specification audit, and migration validation. A frequent pattern retrieves all active composite specification displays for a given event specification disposition:

  • SELECT COMPOSITE_SPEC_DISP_ID, DISPOSITION, LOT_STATUS FROM GMD.GMD_COMPOSITE_SPEC_DISP WHERE EVENT_SPEC_DISP_ID = :event_id AND DELETE_MARK = 0;
  • SELECT * FROM GMD.GMD_COMPOSITE_SPEC_DISP WHERE LATEST_IND = 'Y' AND LAST_UPDATE_DATE >= :from_date;
  • Joins to disposition and specification tables using EVENT_SPEC_DISP_ID and COMPOSITE_SPEC_DISP_ID are common for building quality dashboards and validating that composite specifications are correctly linked to their disposition events.

Because the table is small and heavily keyed, it is well suited to lookup-style reporting and to driving LOV queries in custom concurrent programs.

Related Objects

The documented relationship classification is standalone, so no parent FK chain is asserted in the metadata. In practice, significant related objects include:

  • GMD_EVENT_SPEC_DISP — joined via EVENT_SPEC_DISP_ID.
  • GMD_COMPOSITE_SPEC — joined via COMPOSITE_SPEC_DISP_ID.
  • GMD_SPEC_DISP — shares disposition logic referenced by DISPOSITION.
  • GMD_QUALITY_SPECS and related quality specification tables — dependent on composite specification resolution.
  • QM_LOTS / lot status sources — supply LOT_STATUS values consumed by this table.
  • APIs and concurrent programs that process composite quality specifications for OPM readers.