P2P Cycle Internal Demand----Requisition-----Request For Quotation-----Quotation-----Auto Create----Purchase Order----Receipt-----Receiving----Invoice-----Payment----Bank Reconciliation

PO Types Purchase Order Types Oracle Purchasing provides the following purchase order types: Standard Purchase Order, Planned Purchase Order, Blanket Purchase Agreement and Contract Purchase Agreement. You can use the Document Name field in the Document Types window to change the names of these documents. For example, if you enter Regular Purchase Order in the Document Name field for the Standard Purchase Order type, your choices in the Type field in the Purchase Orders window will be Regular Purchase Order, Planned Purchase Order, Blanket Purchase Agreement and Contract Purchase Agreement

Standard Purchase Orders You generally create standard purchase orders for onetime purchase of various items. You create standard purchase orders when you know the details of the goods or services you require, estimated costs, quantities, delivery schedules, and accounting distributions. If you use encumbrance accounting, the purchase order may be encumbered since the required information is known

Blanket Purchase Agreements (BPA) You create blanket purchase agreements when you know the detail of the goods or services you plan to buy from a specific supplier in a period, but you do not yet know the detail of your delivery schedules. You can use blanket purchase agreements to specify negotiated prices for your items before actually purchasing them. BPA are widely used in product manufacturing companies.

You can issue a blanket release against a blanket purchase agreement to place the actual order (as long as the release is within the blanket agreement effectivety dates). If you use encumbrance accounting, you can encumber each release

Contract Purchase Agreements You create contract purchase agreements with your suppliers to agree on specific terms and conditions without indicating the goods and services that you will be purchasing. You can later issue standard purchase orders referencing your contracts, and you can encumber these purchase orders if you use encumbrance accounting

Planned Purchase Order You create a planned purchase order when you want to establish a long term agreement with a single source supplier with a commitment to buy goods or services. Planned purchase orders include tentative delivery schedules and accounting distributions. You then create scheduled releases against the planned purchase order to actually order the goods or services.

A planned purchase order is a type of purchase order you issue before you order actual delivery of goods and services for specific dates and locations. A scheduled release is issued against a planned purchase order to place the actual order. You can also change the accounting distributions on each release and the system will reverse the encumbrance for the planned purchase order and create a new encumbrance for the release

po_requisition_headers_all po_requisition_lines_all po_req_distributions_all po_headers_all po_lines_all po_line_locations_all po_distributions_all rcv_transactions rcv_shipment_headers rcv_shipment_lines

Interface Tables ============= po_requisitions_interface_all po_reschedule_interface po_headers_interface po_lines_interface po_distributions_interface Receipts RCV_SHIPMENT_HEADERS stores common information about the source of your receipts or expected receipts. You group your receipts by the source type and the source of the receipt. Oracle Purchasing does not allow you to group receipts from different sources under one receipt header. . There are two receipt source types, Supplier and Internal Order, that you need to use when receiving against different source document types. You use a receipt source type of 'Supplier' when receiving items that you ordered from an external supplier using a purchase order. When you receive items that are part of an inter-organization transfer, or when receiving items that you request from your inventory using an internal requisition, the receipt type would be 'Internal Order. The 'Internal Order' receipt source type populates the ORGANIZATION_ID column. . Oracle Purchasing creates a receipt header when you are entering your receipts or when you perform inter-organization transfers using Oracle Inventory. When Oracle Inventory creates a receipt header for an intransit shipment, the receipt number is not populated until you receive the shipment. RCV_SHIPMENT_LINES stores information about items that have been shipped and/or received from a specific receipt source. . RCV_SHIPMENT_LINES also stores information about the default destination for intransit shipments. Receipt Transactions RCV_TRANSACTIONS stores historical information about receiving transactions that you have performed. When you enter a receiving transaction 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 transaction quantity is maintained in RCV_SUPPLY. The original transaction quantity does not get updated. You can only delete rows from this table using the Purge feature of Oracle Purchasing.

Other important tables PO_SYSTEM_PARAMETERS_ALL PO_SYSTEM_PARAMETERS_ALL stores default, control, and option information you provide to customize Oracle Purchasing to your companys needs. PO_SYSTEM_PARAMETERS_ALL corresponds to the Purchasing Options window. This table has no primary key. The table should never have more than one row.

PO_UNIQUE_IDENTIFIER_CONT_ALL PO_UNIQUE_IDENTIFIER_CONT_ALL stores information about the current, highest, systemgenerated numbers for the Oracle Purchasing tables that require special sequencing. You need one row for each sequentially systemgenerated number for each organization. The table includes rows for each of the following: purchase orders, requisitions, receipts, suppliers, quotations, and requests for quotations (RFQs). For each organization, there are four rows for each of the following entities: PO_HEADERS_ALL, PO_REQUISITION_HEADERS_ALL, PO_HEADERS_RFQ and PO_HEADERS_QUOTE. There are two rows corresponding to the entities PO_VENDORS and RCV_SHIPMENT_HEADERS. The information for the quotation and RFQ subentities is associated with the PO_HEADERS_ALL table entity. TABLE_NAME values for quotations and RFQs are PO_HEADERS_QUOTE and PO_HEADERS_RFQ respectively. PO_LINE_TYPES_B PO_LINE_TYPES_B contains information about the line types you use in your business. You need each row for each line type you use. Oracle Purchasing uses this information to provide default information when you create a document line using a line type. Oracle Purchasing also uses this information to control how you enter information on your document lines according to the line type you choose. ORDER_TYPE_LOOKUP_CODE is AMOUNT for an amountbased line type or QUANTITY for a quantitybased line type. PO_DOCUMENT_TYPES_B PO_DOCUMENT_TYPES_ALL_B contains information about default, control, and option information you provide to customize Oracle Purchasing document management for your companys needs. PO_DOCUMENT_TYPES_ALL_B corresponds to the Document Types window. PO_ACTION_HISTORY PO_ACTION_HISTORY contains information about the approval and control history of your purchasing documents. There is one record in this table for each approval or control action an employee takes on a purchase order, purchase agreement, release, or requisition. Each row includes references to the document itself, the employee who acted on the document, the date of the

action, the type of action taken on the document, and a note each employee can leave when taking an action on the document. Oracle Purchasing uses this information to display history information about documents and to forward documents in the approval process to the appropriate employee.