This document summarizes the key tables and steps involved in the procure-to-pay (P2P) process in Oracle Applications, including creating a requisition, purchase order, goods receipt, invoice, payment, and general ledger transfer. It provides descriptions of over 15 tables used to store header and line item information at each stage of the process, as well as important columns within each table.

1. P2P :( procure to pay)
 Create Requisition
 Create Purchase Order
 Create InventoryReceipt
 Enter AP Invoice
 Make Payment
 TransfertoGL
1. Create requisition:
Headers - po_requisition_headers_all
Lines - po_requisition_lines_all
Distribution- po_req_distribution_all
>> Po_requisition_headers_all:
Important columns:
Requisition_header_id: requisitionheaderunique identifier.
Segment1: requisitionnumber.
Authorization_status: authorizationtype. (Complete)
Type_lookup_code: requisitiontype. (Purchaseandinternal)
Description:
PO_REQUISITION_HEADERS_ALLstores information about requisitionheaders.
>>Po_requisition_lines_all:
Important columns:
Requisition_header_id: requisitionheaderunique identifier.
Line_type_id: line type (goods).
Quantity_number: quantityordered.
Categeory_id: itemcategory unique identifier.
Description:
PO_REQUISITION_lines stores informationabout requisition lines. Eachrowcontains theline number, item number, itemcategory,
item description, need-by date, deliver-tolocation, itemquantities, units, prices, requestor, notes, andsuggestedsupplier informationforthe
requisition line.
>>po_req_distribution_all:
Important columns:
Distribution_id: requisitiondistributionunique identifier.
Requisition_line_id: requisition lineunique identifier.
Code_combination_id: unique identifier for thegeneral ledger.
Distribution_num: distributionnumber.
Description:
Po_req_distribution_all stores information about the accountingdistributionassociatedwith each requisitionline.Eachrequisition line must
have at least one accountingdistribution.
Po_req_distribution_all is one of three tables storingyour requisitionnumber.
Accountingdistribution:
Accountingdistributions are usedto define howan amount will be accountedfor,such as howthe expense, tax, or charges will be
accountedforon a vendorinvoice. Everyamount that must be accountedfor when thevendor invoice is journalizedwill have oneor
more accountingdistributions
2. Create purchase order:
Header: po_headers_all
Line: po_lines_all
Distribution: po_distribution_all

2. >>po_headers_all:
Important columns:
Po_header_id
Segment1
Vendor_id
Vendor_site_id
Description:
Po_headers_all contains header information for all purchasingdocuments. There aresix types ofdocuments that use po_headers_all.
 RFQs
 Quotations
 Standardpurchase orders
 Plannedpurchase orders
 Blanket purchase orders
 Contracts
>>po_lines_all:
Important columns:
Po_line_id: document the unique identifier.
Po_header_id: document header unique identifier. (Reference po_headers_all ,po_header_id)
Item_id: itemunique identifier.
Line_num: line number.
Description:
Po_lines_all stores current informationabout eachorder purchase order line.there are fivedocument types that use line.
 RFQs
 Quotations
 Standardpurchase orders
 Blanket purchase orders
 Plannedpurchase orders
>>po_distribution_all:
Important columns:
Po_distribution_id: document distributionunique identifier.Primarykeyforthis table.
Po_header_id: document header unique identifier. Reference po_headers_all.po_header_id.
Po_line_id: document the unique identifier. Reference po_lines_all.po_lines_id.
Line_location_id:
Description:
Po_distribution_all contains accountingdistributioninformationfor a purchase order shipment line.
3. Create the receipt:
Headers: RCV_SHIPMENT_HEADERS
Lines: RCV_SHIPMENT_LINES
Transaction: rcv_transactions
>>Rcv_shipment_headers:
Important columns:
Shipment_header_id: receipt header unique identifier.
Receipt_source_code: sourcetypeof the shipment – vendor,internal orderor customer.
Vendor_id: source supplier unique identifier.
Shipment_num: shipment number.
Receipt_num: receipt number.
Description:
Rcv_shipment_headers stores commoninformationabout thesource ofyour receipts or expectedreceipts.
There are two receipt source types, supplier andinternal order.

3. >>Rcv_shipment_lines:
Important columns:
Shipment_line_id: shipment line unique identifier.
Item_id: itemidentifier.
Vendor_item_num: suppliers item number.
Shipment_line_status_code: receipt status of the shipment line
Description:
Rcv_shipment_lines stores informationabout items that have been shipped.
>>Rcv_transaction:
Important columns:
Transaction_id: receivingtransactionunique identifier.
Request_id:
Transaction_type: receivingtransactiontype.
Transaction_date:
Quantity:
Description:
Rcv_transaction stores historical information about receivingtransactionthat youhave performed.
4. Invoices:
>>ap_invoices_all:
Important columns:
Invoice_id: generatedusinga database sequences.
Vendor_id:
Invoice_num:
Set_of_books_id:
Payment_currency_code:
Description:
This table corresponds to the Invoices header blockofInvoice workbench. AP_INVOICES_ALLholds information this table corresponds
to the Invoices header blockof Invoice workbench.AP_INVOICES_ALL holds information Oracle Projects,Supplier Portal, Refunds from
Oracle Receivables etc.This table holds all type ofinvoices, which includes Standard, Prepayments, Credit Memo,Debit Memo, Mixedinvoice,
Withholdinginvoice, Interest Invoice, Retainage invoices, Payment Requests etc.,
>>ap_invoice_distributions_all:
Important columns:
Invoice_id: Unique invoicedistributionidentifier.
SET_OF_BOOKS_ID: Ledger identifier ofthe invoice distribution.
AMOUNT: Amount on invoice distribution.
INVOICE_DISTRIBUTION_ID:
Description:
AP_INVOICE_DISTRIBUTIONS_ALL holds the distributioninformationthat is manuallyenteredorsystem-generated.
>>ap_checks_all:
Important columns:
Amount: payment amount
Bank_account_id: longer used
Bank_account_name:
Check_id_number:
Check_number: paymnt number
Vendor_name: suppliername
Vendor_site_code: supplier site code
Descriptions:
Ap_checks_all stores information about payment issuedto suppliers or refundreceivedfromsuppliers.
>>ap_invoice_payments_all:
Important columns:
Invoice_payment_id:
Invoice_id:
Check_id:
Payment_num:

4. Descriptions:
Ap_invoice_payments_all contains recordofinvoicepayments that youmade tosuppliers.
>>ap_payment_schedules_all:
Important columns:
Invoice_id:
Payment_num:
Amount_remaining:
Descriptions:
Ap_payment_schedules_all contain information about scheduledfor aninvoice.
5. GL Transfer:
>>gl_periods:
Important columns:
Period_set_name: name ofthe accountingcalendar.
Period_name: systemgeneratedaccountingperiodname.
Descriptions:
Gl_periods contains information about the accountingperiods that are definedusingthe accountingcalendarform.
>>gl_period_statuses:
Important columns:
Application_id: identifier associatedwith the application
Ledger_id: unique identifier of the ledger
Period_name:
Descriptions:
Gl_period_statuses contains the statuses of youraccountingperiods.
>>gl_set_of_books:
Important_columns: