procure to pay tables and data flow

7/31/2019 Procure to Pay Tables and Data Flow

1/4

Procure to Pay Tables and Data Flow

Vendors

SELECT * FROM ap_vendors_v WHERE vendor_name = 'XX_VENDOR';

select * from po_vendors where vendor_name = 'XX_VENDOR';

Requisitions

select segment1, type_lookup_code,a.* from po_requisition_headers_all a where requisition_header_id =&Requisition_Header_ID;

select * from po_requisition_lines_all where requisition_header_id = &Requisition_Header_ID andrequisition_line_id = &Requisition_Line_ID;

select * from po_req_distributions_all where requisition_line_id = &Requisition_Line_ID;

select * from po_document_types where document_subtype = 'PURCHASE';--(po_requisition_headers_all.type_lookup_code)

select * from po_lookup_codes where lookup_type = 'AUTHORIZATION STATUS';

PO tables

select * from po_headers_all where po_header_id = &the_PO_Header_ID; select * from po_lines_all where po_header_id =&the_PO_Header_ID; select * from po_line_locations_all where po_header_id = &the_PO_Header_ID;

select * from po_distributions_all where po_header_id = &the_PO_Header_ID;

select * From po_headers_all where po_header_id = &po_header_id; select * from po_lines_all where po_line_id = &po_line_id;

select * from po_line_locations_all where po_header_id = &po_header_id; select * from po_distributions_all where req_distribution_id = po_req_distributions_all.distribution_id // you can

get the Po_Distribution_ID

Receiving

select * from rcv_transactions where po_header_id = &the_PO_Header_ID and po_distribution_id =&Po_Distribution_ID;

select * from rcv_shipment_headers where shipment_header_id = rcv_transaction.shipment_header_id; select * from rcv_shipment_lines where where shipment_header_id = rcv_transaction.shipment_header_id; select * from rcv_serial_transactions where transaction_id = rcv.transactions.transaction_id;

Receiving transaction Processor import


2/4

AP Invoices and Payments

select * from ap_invoice_distributions_all where po_distribution_id = &Po_Distribution_ID;

select * from ap_invoices_all where invoice_id = &Invoice_ID;

select * from ap_terms where term_id = &Term_ID; select * from ap_invoice_payments_all where invoice_id = &Invoice_ID; select * from ap_payment_schedules_all where invoice_id = &Invoice_ID;

select * from ap_payment_distributions_all where invoice_payment_id in (select invoice_payment_id fromap_invoice_payments_all where invoice_id = &Invoice_ID);

select * from ap_checks_all where check_id = &Check_ID;

Accounting Entries

select * from ap_ae_lines_all where source_table = 'AP_INVOICES' and source_id = &Invoice_ID; --(ap_invoices_all.invoice_id)

select * from ap_ae_headers_all where ae_header_id = &ae_header_ID;

Reconciling Bank Accounts in Cash Management Module

select * from ce_statement_headers_all where statement_header_id =&statement_header_id select * from ce_statement_lines where statement_header_id in (select statement_header_id from

ce_statement_headers_all where statement_header_id =&statement_header_id)

Concurrent Program "Payables Transfer to General Ledger"

select * from gl_interface;

Import Journal

select * from gl_je_batches; select * from gl_je_headers;

select * from gl_je_lines;

Post Journals "Posting"

select * from gl_balances;


3/4

Requisition Screen Header

select * from PO_REQUISITION_HEADERS_INQ_V where requisition_num = '&Requisition_Number';

select * from PO_REQUISITION_LINES_INQ_V where requisition_header_id = &Requisition_Header_ID;

select * from PO_REQUISITION_HEADERS_V where requisition_number = '&Requisition_Number'; select * from PO_REQUISITION_LINES_V where requisit ion_header_id = &Requisition_Header_ID; select * from PO_REQ_DISTRIBUTIONS_V where requisition_line_id in (select requisition_line_id from

PO_REQUISITION_LINES_V where requisition_header_id = &Requisition_Header_ID);

Puchasing and Payables integration : Technical tables

PO_VENDORSThis table stores information about your suppliers. Oracle Purchasing uses this information to determine active suppliers.The primary key is VENDOR_ID.

PO_VENDOR_SITES_ALLThis table stores information about supplier sites. Oracle Purchasing uses this information to store supplier addressinformation. The primary key is VENDOR_SITE_ID.

PO_VENDOR_CONTACTSThis table stores information about supplier site contacts. The primary key is VENDOR_CONTACT_ID.

PO_REQUISITION_HEADERS_ALLPO_REQUISITION_HEADERS_ALL stores information about requisition headers. Each row contains the requisitionnumber, preparer status, and description. It is one of three tables that stores requisition information. The primary key isREQUISITION_HEADER_ID.

PO_REQUISITION_LINES_ALLThis table stores information about requisition lines. Each row contains the line number, item number, item category, itemdescription, need-by date, deliver-to location, item quantities, units, prices, requestor, notes, and suggested supplier

information for the requisition line. This table is one of three tables that stores requisition information. The primary key isREQUISITION_LINE_ID.

PO_REQ_DISTRIBUTIONS_ALLPO_REQ_DISTRIBUTIONS_ALL stores information about the accounting distributions associated with each requisition line.Each requisition line must have at least one accounting distribution. Each row includes the Accounting Flex field ID andrequisition line quantity. This table is one of three tables that stores requisition information. The primary key isDISTRIBUTION_ID.

PO_HEADERS_ALLPO_HEADERS_ALL contains information for your purchasing documents. Each row contains buyer information, supplierinformation, notes, foreign currency information, terms and conditions information, and the document status. OraclePurchasing uses this information to record information related to a complete document. The primary key is PO-HEADER_ID.

PO_LINES_ALL

PO_LINES_ALL stores current information about each purchase order line. You need one row for each line you attach to adocument. Each row includes the line number, item number and category unit, price, tax information, and quantity orderedfor the line. Oracle Purchasing uses this information to record and update item and price information for purchase orders,quotations, and RFQs. The primary key is PO_LINE_ID.

PO_LINE_LOCATIONS_ALLThis table contains information about purchase order shipment schedules and blanket agreement price breaks. You musthave one row for each schedule or price break you attach to a document line. Each row contains the location, quantity, anddates for each shipment schedule. Oracle Purchasing uses this information to record delivery schedule information forpurchase orders and price break information for blanket purchase orders, quotations, and RFQs. The primary key isLINE_LOCATION_ID.


4/4

PO_DISTRIBUTIONS_ALLPO_DISTRIBUTIONS_ALL contains accounting information for a purchase order shipment line. Oracle Purchasing uses thisinformation to record accounting and requisition information for purchase orders and releases. It is one of five tables thatstores purchase orders and releases. The primary key is PO_DISTRIBUTION_ID.

RCV_SHIPMENT_HEADERSThis table stores common information about the source of your receipts or expected receipts. You group your receipts by thesource type and the source of the receipt. Oracle Purchasing does not allow you to group receipts from different sources

under one receipt header. The primary key is SHIPMENT_HEADER_ID.

RCV_SHIPMENT_LINESThis table stores information about items that have been shipped or received from a specific receipt source. This table alsostores information about the default destination for in-transit shipments. The primary key is SHIPMENT_LINE_ID.

RCV_TRANSACTIONSThis table stores historical information about receiving transactions that you have performed. When you enter a receivingtransaction and the receiving transaction processor processes your transaction, the transaction is recorded in this table.Once a row has been inserted into this table, it will never be updated. When you correct a transaction, the net transactionquantity is maintained in RCV_SUPPLY. The original transaction does not get updated. You can only delete rows from thistable using the Purge feature of Oracle Purchasing. The primary key is TRANSACTION_ID.

PO_RELEASES_ALLThis table contains information about blanket and planned purchase order releases. You need one row for each release you

issue for a blanket or planned purchase order. Each row includes the buyer, date, release status, and release number. Eachrelease must have at least one purchase order shipment (PO_LINE_LOCATIONS_ALL). The primary key isPO_RELEASE_ID.

AP_INVOICES_ALLThis table contains records for supplier invoices and has one row for each invoice. To pass Invoice Validation, theINVOICE_AMOUNT in the AP_INVOICES_ALL table must equal the sum of the AMOUNT columns in theAP_DISTRIBUTIONS_ALL table. The primary key is INVOICE_ID.

AP_INVOICE_DISTRIBUTIONS_ALLThis table holds the distribution line information.There is a row for each invoice distribution. If matching is used, distribution information is copied fromPO_DISTRIBUTIONS_ALL during the matching process.

AP_PAYMENT_SCHEDULES_ALLThis table contains information about scheduled payments for an invoice.

Oracle Payables uses this information to determine when to make payments on an invoice and how much to pay in anautomatic payment batch.

AP_HOLDS_ALLThis table contains a record for each hold placed on an invoice.An invoice might have multiple records in this table.Aninvoice cannot be paid until all holds placed on it have been released.

AP_CHECKS_ALLThis table stores information about payments issued to suppliers.Each row includes the supplier name, address, and bankaccount name for auditing purposes, in case any of them change after you make the payment.If the payment is electronic,the supplier bank account information is stored in the payment record.

AP_INVOICE_PAYMENTS_ALLThis table provides the link between a payment (CHECK_ID) and the invoice(s) paid by that payment.This table containsrecords of invoice payments that you make to suppliers. Oracle Payables updates this table when you confirm an automaticpayment batch, enter a manual payment, or process a Quick Payment. This table contains one row for each payment madefor each invoice.Void payments are also entered into this table as a negative record of the original payment line.

AP_BANK_ACCOUNTS_ALLThis table stores information about your bank accounts and your suppliers and customers bank accounts. This tablecontains one row for every bank account, whether it is an internal (supplier) or external (customer) account.

AP_BANK_BRANCHESThis table stores information about the bank branches and details about the branches.

procure to pay tables and data flow

Documents