Search Results po_multi_mod_val_results




Overview
Explore in AI Chat

Overview

PO_MULTI_MOD_VAL_RESULTS is a Purchasing (PO) module table in the Oracle E-Business Suite 12.1.1 and 12.2.2 schemas, owned by the PO schema. It stores Supplier exceptions generated for a Multiple Modifications Request. When the Multiple Modifications feature is used to apply mass updates across several purchase orders, blanket agreements, or other sourcing documents, Oracle runs validation logic against each affected document line and records any exceptions, warnings, or blocking conditions into this table.

From a Data Vault modeling perspective, the table carries a heuristic classification of standalone. In practice, it behaves as a transactional satellite-like store of validation results, keyed to the parent Multiple Modifications request and document. Because the mined relationships point solely at PO_MULTI_MOD_REQUESTS and PO_MULTI_MOD_DOCS, the classification is best treated as a suggestion rather than a strict architectural rule; the table is functionally dependent on the batches it validates.

Key Information Stored

The surrogate primary key is MULTI_MOD_VAL_RESULT_ID, enforced through the PO_MULTI_MOD_VAL_RESULTS_PK constraint. The business context is established by two foreign keys: MULTI_MOD_REQUEST_ID, which links the exception back to PO_MULTI_MOD_REQUESTS, and MULTI_MOD_DOC_ID, which links it to PO_MULTI_MOD_DOCS.

The table contains 32 columns in total as documented for ETRM 12.2.2.

Common Use Cases and Queries

Typical reporting scenarios include troubleshooting failed Multiple Modifications submissions, auditing which documents triggered conflicts, and analyzing recurring exception patterns by validation type. A representative query joins the results table to its request parent:

SELECT r.multi_mod_val_result_id, r.multi_mod_request_id, r.document_number, r.validation_type, r.exception_type, r.message_name FROM po.po_multi_mod_val_results r WHERE r.multi_mod_request_id = :request_id ORDER BY r.multi_mod_val_result_id;

Analysts may aggregate counts by EXCEPTION_TYPE to gauge error density across a batch, or filter on RESULT_TYPE to isolate blocking errors from advisory warnings. Because the table carries REQUEST_ID and CREATED_BY, it supports concurrency auditing and Segregation of Duties review.

Related Objects

  • PO_MULTI_MOD_REQUESTS — parent table; join on MULTI_MOD_REQUEST_ID = PO_MULTI_MOD_REQUESTS.MULTI_MOD_REQUEST_ID.
  • PO_MULTI_MOD_DOCS — child document table; join on MULTI_MOD_DOC_ID = PO_MULTI_MOD_DOCS.MULTI_MOD_DOC_ID.
  • FND_MESSAGES / FND_NEW_MESSAGES — resolve MESSAGE_NAME and MESSAGE_APPLICATION into readable text.
  • PO_HEADERS_ALL and PO_LINES_ALL — resolve DOCUMENT_ID to the underlying purchasing documents and lines.
  • FND_CONCURRENT_REQUESTS — resolve REQUEST_ID for concurrent program tracking.