Results for “processed_ind”

50+ results




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

Overview

GML_RECV_ADJUST_ERRORS is a table in the GML schema (Process Manufacturing Logistics) that stores error records generated during the adjustment of OPM receipt quantities. When the Process Manufacturing receipt adjustment process encounters a discrepancy — for example a mismatch between the requested new quantity and the receipt quantity currently recorded, an invalid unit of measure, or a status that prevents the update — the failing row is written to this table rather than aborting the entire run. The table therefore acts as a diagnostic and reconciliation log for receipt correction activity.

The table resides in the GML schema and is marked VALID in the ETRM 12.2.2 documentation. The documented physical schema lists 15 columns, with a single unique index, GML_RECV_ADJUST_ERRORS_PK, defined on (RECV_ID, LINE_ID, SEQ_NO). Based on the mined foreign-key structure, the Data Vault classification heuristic suggests treating this object as a standalone structure; that is, it is best modeled as an independent table rather than decomposed into hub, link, and satellite constructs, because no parent-child FK dependencies to other entities were identified. The composite primary key nonetheless carries the natural identifier of the affected receipt line.

Key Information Stored

The primary key is the composite GML_RECV_ADJUST_ERRORS_PK, formed from three columns: RECV_ID identifies the receiving transaction, LINE_ID identifies the specific receipt line within that transaction, and SEQ_NO distinguishes multiple error occurrences against the same line. These three columns are also the only documented business-key candidates, since the PK is the sole unique index in the metadata.

The quantity-related columns capture the substance of the failed adjustment. RECV_QTY1 holds the new (attempted) receipt quantity, while OLD_RECV_QTY1 preserves the quantity in effect before the adjustment was requested, making it possible to reconstruct exactly what change was being applied. RECV_UM1 records the unit of measure associated with the quantity. RECV_STATUS and PROCESSED_IND describe the state of the record: RECV_STATUS conveys the receipt status at the time of failure, and PROCESSED_IND indicates whether the error row has since been reviewed or reprocessed. RETURN_IND and VOID_RETURN_IND are flags relating to return and void-return processing against the receipt.

Standard Oracle EBS auditing columns are also present: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN. These establish who and when the error row was created and last touched, which is essential for support and audit trails.

Common Use Cases and Queries

The most frequent use is triage of failed receipt adjustments. A typical query lists unprocessed errors for a given receipt:

  • SELECT recv_id, line_id, seq_no, recv_qty1, old_recv_qty1, recv_um1, recv_status FROM gml.gml_recv_adjust_errors WHERE processed_ind = 'N' ORDER BY creation_date DESC;
  • Joining back to the receipt line to compare the stored quantity with the current receipt balance, and reviewing RETURN_IND / VOID_RETURN_IND where return processing is implicated.
  • Ageing or volume reporting by CREATED_BY and CREATION_DATE to identify systemic adjustment problems introduced by a specific interface or user.

Because the table has no dependent foreign keys, reporting is generally performed standalone or by manually joining RECV_ID and LINE_ID to the OPM receiving tables.

Related Objects

Although the metadata classifies the table as standalone, the primary key columns reference the OPM receiving data model. The most significant related objects are the receipt header and line tables keyed on RECV_ID and LINE_ID (such as the OPM receiving transactions and receipt line tables), the receipt adjustment processing program that populates this table, and the inventory transaction and unit-of-measure tables referenced through RECV_UM1. Reconciliation reports and interfaces over OPM receiving typically query this table alongside the receipt quantity tables to detect and resolve outstanding adjustment failures.