Results for “oper_id”

4 results




Overview
Explore in AI Chat

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

Overview

The GMO_AREA_OPERATOR_MAPPING table is a Manufacturing Execution System (MES) configuration object within the Oracle E-Business Suite Process Manufacturing (OPM) module, owned by the GMO schema. It defines the authorized relationship between a dispense area and the operators permitted to work within that area, forming a control mechanism for shop-floor dispense activities. In release 12.1.1 and 12.2.2, this table is referenced by the MES dispense workstation logic to restrict and register which personnel may execute dispensing tasks for a given staging or weigh area.

The table carries a heuristic Data Vault classification of standalone, as mined from its foreign-key structure. From a modeling perspective, this suggests the object behaves as a self-contained link-style association between two business concepts (dispense area and operator), rather than depending on parent hubs through declarative constraints. The composite primary key GMO_AREA_OPERATOR_MAPPING_PK over (DISPENSE_AREA_ID, OPER_ID) reinforces this many-to-many association interpretation.

Key Information Stored

The documented physical schema contains eight columns. The most significant are described below.

  • DISPENSE_AREA_ID — Identifier of the dispense area; part of the composite primary key and the principal search column when the term "dispense_area_id" is queried. It anchors the mapping to a specific physical or logical dispensing zone.
  • OPER_ID — Identifier of the operator (personnel resource) authorized against the area; the second component of the composite primary key.
  • NUMBER_OF_TASKS_PER_DAY — Optional operational parameter expressing the expected or permitted task count per day for the area/operator combination, used for workload planning or enforcement.
  • CREATED_BY / CREATION_DATE — Standard EBS audit columns recording the creating user and timestamp.
  • LAST_UPDATED_BY / LAST_UPDATE_DATE — Standard EBS audit columns recording the most recent modifying user and timestamp.
  • LAST_UPDATE_LOGIN — The login identifier associated with the last update, supporting session-level traceability.

The surrogate/primary key is the composite GMO_AREA_OPERATOR_MAPPING_PK (DISPENSE_AREA_ID, OPER_ID), which is also documented as the sole unique index and therefore the business-key candidate. No additional unique constraints are documented.

Common Use Cases and Queries

Typical scenarios include validating operator authorization at a dispense station, reporting area-level staffing, and auditing mapped assignments. A query to list all operators for a specific dispense area follows:

  • SELECT OPER_ID, NUMBER_OF_TASKS_PER_DAY FROM GMO_AREA_OPERATOR_MAPPING WHERE DISPENSE_AREA_ID = :p_area_id;
  • SELECT DISPENSE_AREA_ID, COUNT(*) FROM GMO_AREA_OPERATOR_MAPPING GROUP BY DISPENSE_AREA_ID; — area staffing summary.
  • SELECT m.* FROM GMO_AREA_OPERATOR_MAPPING m WHERE m.OPER_ID = :p_oper_id; — all areas an operator is authorized for.
  • Reporting the LAST_UPDATE_DATE range to audit recent mapping changes.

Related Objects

Because the documented classification is standalone with no mined foreign keys, related objects are inferred from naming and OPM MES context. The most significant are: