Search Results po_requisitions_interface_all




Overview
Explore in AI Chat

Overview

The PO_REQUISITIONS_INTERFACE_ALL table is a critical interface table within the Oracle E-Business Suite Purchasing (PO) module, serving as the staging area for requisition data import. Its primary role is to facilitate the batch loading of requisition data from external, non-Oracle systems or from internal legacy applications into the core Oracle Purchasing tables. Data is populated into this table via custom programs, SQL*Loader scripts, or other data migration tools. Subsequently, the standard Requisition Import concurrent program (REQIMPORT) processes the records from this interface table, validates the data against Oracle's business rules, and creates approved requisitions in the transactional tables PO_REQUISITION_HEADERS_ALL and PO_REQUISITION_LINES_ALL. The '_ALL' suffix indicates it is a multi-organization table, storing data partitioned by Operating Unit (ORG_ID).

Key Information Stored

The table stores a comprehensive set of requisition attributes, mirroring the fields found in the transactional requisition tables. The TRANSACTION_ID column serves as the primary key, uniquely identifying each interface record. Key columns include REQUISITION_HEADER_ID and REQUISITION_LINE_ID for linking to existing requisitions during updates, and REQ_DISTRIBUTION_ID for distribution-level updates. It holds sourcing suggestions (SUGGESTED_BUYER_ID, SUGGESTED_VENDOR_ID), item details (CATEGORY_ID), delivery information (DESTINATION_ORGANIZATION_ID, DESTINATION_SUBINVENTORY), and accounting data (ACCRUAL_ACCOUNT_ID, VARIANCE_ACCOUNT_ID). Interface control columns like BATCH_ID, PROCESS_CODE, and INTERFACE_SOURCE_CODE manage the import process flow and error handling.

Common Use Cases and Queries

The principal use case is the automated creation and update of purchase requisitions. A typical implementation involves writing a custom PL/SQL procedure or using a tool to populate the interface table, followed by a submission of the Requisition Import program. Common diagnostic queries include checking for records pending import or those that have errored. For example:

  • To identify records in error: SELECT transaction_id, error_message FROM po_requisitions_interface_all WHERE process_code = 'ERROR';
  • To review unprocessed records for a specific batch: SELECT * FROM po_requisitions_interface_all WHERE batch_id = &batch_id AND process_code IS NULL;
  • To purge successfully processed records: DELETE FROM po_requisitions_interface_all WHERE process_code = 'PROCESSED';

Reporting directly from this table is uncommon, as it is a transient staging area; reports should query the transactional requisition tables after successful import.

Related Objects

As indicated by its foreign keys, PO_REQUISITIONS_INTERFACE_ALL has extensive relationships with core Purchasing and Inventory entities. It is the direct source for the Requisition Import program, which writes to the transactional tables PO_REQUISITION_HEADERS_ALL and PO_REQUISITION_LINES_ALL. Key referenced tables include MTL_CATEGORIES_B for item categories, PO_AGENTS for buyers, PO_VENDORS and PO_VENDOR_SITES_ALL for supplier information, and GL_CODE_COMBINATIONS for accounting flexfields. For managing hazardous materials, it references PO_UN_NUMBERS_B and PO_HAZARD_CLASSES_B. The table PO_REQ_DISTRIBUTIONS_ALL is linked for distribution-level interface data. The primary integration point for developers is the Requisition Import Open Interface, not direct DML on this table.