Results for “validation_id”

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

Overview

PO_VALIDATION_RESULTS_GT is a Global Temporary Table (indicated by the _GT suffix) owned by the PO schema within Oracle Purchasing. It serves as an intermediate staging and messaging structure that captures the outcome of document validation routines executed during purchasing transaction processing. Rather than acting as a permanent transactional store, this table holds row-level validation results — including error, warning, and informational messages — generated while Oracle validates purchasing documents such as requisitions, purchase orders, and their interface records. Because it is a temporary table, its contents are typically scoped to a session or transaction, making it a transient workspace that feeds downstream error-handling and messaging logic within the Purchasing application.

From a Data Vault modeling perspective, the mined foreign key structure classifies this object as standalone. This is a modeling suggestion rather than a prescriptive design: the table references PQH_DE_RESULT_SETS through RESULT_SET_ID, but it does not participate in a dense network of hub/link relationships. In practice it behaves more like a transient satellite of validation activity, holding descriptive message attributes keyed to a result set and a specific entity undergoing validation.

Key Information Stored

The table documents 22 columns organized around a validation result set and the messages produced against it. The most significant are:

• RESULT_SET_ID — Identifies the parent validation result set and forms the foreign key to PQH_DE_RESULT_SETS. This is the principal business-key candidate grouping related validation messages.
• VALIDATION_ID — Identifies the specific validation executed, linking a result to the rule that produced it.
• RESULT_TYPE — Classifies the nature of the result (for example, error versus warning versus information).
• ENTITY_TYPE and ENTITY_ID — Identify the kind of purchasing entity validated and its internal identifier, enabling results to be tied back to the originating document or line.
• ENTITY_INTERFACE_ID — Correlates the result to the corresponding interface (staging) record during inbound processing.
• COLUMN_NAME and COLUMN_VAL — Record the specific attribute and its value that failed or triggered validation, providing field-level diagnostic detail.
• MESSAGE_APPLICATION and MESSAGE_NAME — Reference the message dictionary entries used to render the human-readable text of the result.
• TOKEN1_NAME/TOKEN1_VALUE through TOKEN6_NAME/TOKEN6_VALUE — Supply up to six token substitution pairs that populate placeholders in the message text, allowing a single message definition to convey specific values.

Together, VALIDATION_ID and RESULT_SET_ID act as the strongest business-key candidates, while RESULT_TYPE and ENTITY_TYPE provide the primary filtering dimensions for reporting and troubleshooting.

Common Use Cases and Queries

The table is principally consumed by Oracle Purchasing's validation framework and by support and development personnel troubleshooting document or interface failures. Typical scenarios include diagnosing why a purchase order interface row was rejected, surfacing field-level errors to users, and aggregating validation failures for a batch.

A representative query joining to the parent result set might resemble:

• SELECT v.RESULT_SET_ID, v.ENTITY_TYPE, v.ENTITY_ID, v.COLUMN_NAME, v.COLUMN_VAL, v.MESSAGE_NAME FROM PO_VALIDATION_RESULTS_GT v WHERE v.RESULT_SET_ID = :p_result_set_id;
• Aggregating error counts by RESULT_TYPE for a given ENTITY_INTERFACE_ID to summarize batch health.
• Filtering on MESSAGE_NAME and TOKEN1_VALUE to isolate records associated with a particular validation rule.

Because the table is a global temporary object, queries should be executed within the same session context in which the validation ran; results are not persisted beyond the session or transaction boundary.

Related Objects

• PQH_DE_RESULT_SETS — Referenced through RESULT_SET_ID; the foreign key target that groups validation results.
• PO_INTERFACE_ERRORS — The persistent interface error repository that often receives or mirrors validation feedback during concurrent processing.
• PO_HEADERS_INTERFACE / PO_LINES_INTERFACE — Staging tables whose rows are validated and keyed via ENTITY_INTERFACE_ID.
• FND_NEW_MESSAGES / FND_MESSAGE tokens — Message dictionary objects resolved via MESSAGE_APPLICATION and MESSAGE_NAME.
• PO Document Validation APIs — The validation routines that populate this temporary table during purchasing transaction processing.