Search Results receipt




Overview
Explore in AI Chat

Overview

The GML_RECV_ADJUST_ERRORS table is a critical error-logging entity within the Oracle E-Business Suite Process Manufacturing Logistics (GML) module. It specifically captures and persists error records generated during the adjustment of receipts in the Oracle Process Manufacturing (OPM) environment. Its primary role is to provide a persistent audit trail for transactional failures, enabling system administrators and functional users to diagnose and resolve issues that prevent the successful completion of receipt adjustments. This table is essential for maintaining data integrity and supporting troubleshooting workflows in complex manufacturing logistics operations.

Key Information Stored

The table's structure is defined by its documented primary key, which uniquely identifies each error record. The key columns are:

  • RECV_ID: The primary identifier for the receipt transaction that encountered an error during adjustment. This is a critical foreign key linking to the core receipt transaction table.
  • LINE_ID: Identifies the specific line within the receipt that failed, allowing for granular error analysis.
  • SEQ_NO: A sequence number that provides ordering for multiple error records associated with the same receipt and line.

While the full column list is not detailed in the provided metadata, the primary key structure indicates the table stores error details keyed to the specific receipt (RECV_ID), its line item (LINE_ID), and an instance sequence (SEQ_NO). Additional columns would typically store error messages, error codes, timestamps, and contextual data about the failed adjustment attempt.

Common Use Cases and Queries

The primary use case is investigating and reporting on failed receipt adjustments. System administrators run queries to identify unresolved errors, while support personnel analyze the data to pinpoint root causes. A common reporting pattern involves joining to the main receipt transaction table to pull in receipt numbers and dates for context.

A fundamental diagnostic query would be:

SELECT recv_id, line_id, seq_no, error_message
FROM gml_recv_adjust_errors
WHERE recv_id = :p_recv_id
ORDER BY line_id, seq_no;

For broader operational reporting, a join to a table such as RCV_TRANSACTIONS (or its OPM equivalent) is typical:

SELECT rta.transaction_id, rta.transaction_date, err.*
FROM gml_recv_adjust_errors err,
     rcv_transactions rta
WHERE err.recv_id = rta.transaction_id
AND rta.last_update_date > SYSDATE - 1;

Related Objects

The documented primary key and the column names strongly imply foreign key relationships to core receiving tables. The RECV_ID column is almost certainly a foreign key referencing a primary key, likely TRANSACTION_ID, in a central receiving transactions table such as RCV_TRANSACTIONS or an OPM-specific equivalent like GML_RCV_TRANSACTIONS. Similarly, LINE_ID would reference a line-level table. The table itself is referenced by diagnostic views or purge programs within the GML product family. The primary key constraint GML_RECV_ADJUST_ERRORS_PK enforces the uniqueness of the combination of RECV_ID, LINE_ID, and SEQ_NO.