Oracle E-Business Suite Purchasing and Order Management

PO_REQUISITIONS_INTERFACE_ALL is the interface table used to import requisition lines from external systems or internal requisitions into Oracle Purchasing. PO_INTERFACES_ALL is not the correct interface table for import, and REQUISITIONS_INTERFACE_ALL is incorrect.

In Oracle Purchasing, PO_AUTOCREATE_DOC is the standard PL/SQL package name used by the Create Document Workflow to automatically build purchase orders or releases from approved requisitions. Other options are incorrect or represent different stages.

RMA stands for Return Material Authorization. It is a structured agreement in order management and inventory systems that permits a customer to return items to the supplier for credit, replacement, or repair.

ASL stands for Approved Supplier List in Oracle Purchasing. It is a repository containing relationships between items/commodity codes and the suppliers authorized to provide them, along with specific business rules for each relationship.

Under the Internal Requisitions tab in Purchasing Options, you configure the required Order Type and Order Source used to create internal sales orders from internal requisitions. Numbering options and receipt controls are managed elsewhere in the setup.

The 'Create Internal Sales Orders' concurrent program in Oracle ERP reads approved internal requisition data from the Purchasing interface and creates the corresponding internal sales orders in Order Management. It does not import orders back into Purchasing.

When a requisition is first entered and saved but not yet submitted for approval, its status is Incomplete. This is the initial status before any workflow begins.

Inventory items are accrued at receipt, not at period end. Accrual happens when goods are received to match expense recognition with the receipt of inventory.

RFQ (Request for Quotation) is sent TO suppliers to request quotes. Quotation comes FROM suppliers as their response. These are different document types flowing in opposite directions, so an RFQ cannot be autocreated into a Quotation.

ASL (Approved Supplier List) is not a mandatory prerequisite for creating Contract Agreements. You can create blanket or contract purchase agreements without first defining an ASL, though ASL is useful for automated sourcing.

The Create Releases program is specifically designed to create releases against blanket purchase agreements. It is not used for standard POs, RFQ-to-PO conversion, or copying RFQs to quotations.

When a requisition is finally closed (meaning no further action will be taken), its authorization status becomes Finally Closed. This is distinct from Cancel or regular Closed status.

The Invoice Variance Report specifically shows variances between invoice prices and the original PO prices for inventory and WIP-related invoices. It helps identify discrepancies in what was ordered versus what was billed.

The Receipt Accrual Program is run during Period End Process to accrue receipts for goods received but not yet invoiced. It ensures proper matching of expenses in the accounting period.

Invoice matching options can be configured at multiple levels: globally in Purchasing Options, at the supplier level in Supplier attributes, and at the item level in Item attributes. This provides flexibility in matching rules.

Schedule Ship Date is the date on which the quantity should be available for shipment from the supplier. This is different from Promise Date (when supplier commits delivery) or Arrival Date (when goods reach destination).

Audit Trail is the feature that maintains history of changes made to a purchase order. It tracks who changed what and when, providing a complete change history. Versioning manages different versions, Document Sequence controls numbering, and Mass Update is for bulk changes.

Pick Release is the order management action that triggers the warehouse picking process, notifying personnel that orders are ready to be picked from inventory. This is a standard order fulfillment step that occurs before shipping. Shipping and Booking are different stages, while Invoice is a post-shipment billing activity.

Subinventory transfers in Oracle EBS generally do not require formal approval workflows. These are routine inventory movements between subinventories that can be performed directly unless specific approval controls have been explicitly configured by the organization.

Applying a hold on an order or order line immediately stops all automated workflow processing for that item. The hold prevents any further progress through the fulfillment cycle until it is manually released by an authorized user.