Skip to main content

What are Different Types of Purchase Orders?

Different Types of Purchase Orders

A purchase order (PO) is an official document generated by a buyer of goods/services as an offer for the seller. It becomes a “legal document of contract” once the seller accepts the purchase order. There are mainly 4 different types of purchase orders;
  1. Standard PO
  2. Contract PO
  3. Blanket PO
  4. Planned PO

Standard Purchase Order

It is the most basic and widely used among different types of purchase orders, it is created when a buyer is sure about the order details such as the item, price, delivery schedule, payment terms etc.
Example – Unreal corp. decides to buy 50,000 x 9W led bulbs from GE for a unit price of 10 each to be delivered within 60 days of order date. In such case, Unreal corp. will raise a standard PO and send it to GE for acceptance.  

Contract Purchase Order

It is created for a set period of time (often for a year) the item, pricing, quantity etc. can’t be anticipated precisely. In this case, a contract purchase order can be raised by the buyer, which upon acceptance becomes a legal contract.
During contract period the buyer can raise a standard PO with specifications of requirements and request for goods.
Example – Unreal Corp. analyzes and concludes that it often requires led bulbs of different wattage around different times of the year, however, the requirement is irregular and can’t be anticipated. In this case Unreal corp. can raise a contract purchase order.

Blanket Purchase Order

It is used in cases where the item is known, but quantity and required delivery schedules are unknown. There can be numerous delivery dates against a blanket PO, they are often used in case of large quantities with exceptional discounts.
Example – Unreal corp. decides to buy 5,00,000 x 9W led bulbs each year but they are not sure about the delivery schedule & quantity of each release. In such a situation Unreal corp. will raise a blanket purchase order.

Planned Purchase Order

It is used for a planned purchase anticipated for long-term where the delivery schedule is not known in advance. The dates of delivery can only be anticipated therefore only tentative dates are provided to the seller. Item, pricing and quantity are however known in advance.
Example – Unreal Corp. has evaluated that it will have a long-term need for the next 5 years to buy 25,000 x 11W led bulbs each year. Instead of raising a standard PO each time Unreal Corp. can create a planned purchase order.
The reference table is shown below with different types of purchase orders and their respective scenarios




Labels:

Comments

Post a Comment

Popular posts from this blog

Create Accounting for a Payment generates errors 95333 and 95359

Create Accounting for a Payment generates errors 95333 and 95359 Error: 95333: A conversion rate does not exist to convert USD to AUD for the conversion type Corporate and conversion date 20-MAR-09 for line -25. Please use the Daily Rates form in General Ledger to enter a conversion rate for these currencies, conversion date and conversion type. 95359: There is no accounted amount for the subledger journal entry line. Please inform your system administrator or support representative that: The source assigned to the accounting attribute Accounted Amount has no value for extract line number 88547. Please make sure the source assigned to the accounting attribute Accounted Amount has a valid value, or assign a different source to this accounting attribute. Solution: 1. Specify a conversion rate for the currencies and conversion date mentioned in the error message 95333 Navigation under the General Ledger responsibility: Setup > Currencies > Currency Rates Manager > Daily Rates ...
15 comments
Read more

Public API’s for FA Transactions

Public API’s for FA Transactions So far Oracle FA is have all the good things except the lack on reporting.Oracle FA is now offer lot of public API's that can be used to interfacing with third party or Oracle application other modules. Here are some of transaction's API's:   Additions API if you have requirement to add assets directly via PL/SQL then use  FA_ADDITION_PUB.DO_ADDITION. If you have selected the Allow CIP Assets check box on the Book Controls window of a tax book when adding CIP assets using the Additions API, the this API automatically adds those CIP assets to that tax book at the same time that they are added to the corporate book. Adjustments API you can make cost adjustments to your assetsdirectly via PL/SQL using  FA_ADJUSTMENT_PUB.DO_ADJUSTMENT  for any  process adjustment. Detail can be found in appendix H) You can use this API if you have a custom interface that makes it difficult to use with the existing Oracle Assets interfaces for adjusti...
Post a Comment
Read more

AP Table Relation Oracle Apps

AP Table Relation Oracle Apps ORACLE PAYABLE TABLE RELATION Source Table Dependent Table Condition AP_INVOICE_LINES_ALL AIL ZX_LINES_SUMMARY ZLS AIL.invoice_id = ZLS.trx_id and  ZLS.application_id  = 200 and  ZLS.entity_code  = 'AP_INVOICES' and  ZLS.event_class_code  in ('STANDARD INVOICES', 'PREPAYMENT INVOICES', 'EXPENSE REPORTS') and  AIL.summary_tax_line_id = ZLS.summary_tax_line_id AP_INVOICE_LINES_ALL AIL ZX_LINES ZL AIL.invoice_id = ZL.trx_id and  ZL.application_id  = 200 and  ZL.entity_code  = 'AP_INVOICES' and  ZL.event_class_code  in ('STANDARD INVOICES', 'PREPAYMENT INVOICES', 'EXPENSE REPORTS') and  AIL.line_number = ZL.trx_line_number AP_INVOICE_DISTRIBUTIONS_ALL AID ZX_REC_NREC_DIST ZD AID.invoice_id = ZD.trx_id and  ZD.application_id  = 200 and  ZD.entity_code  = 'AP_INVOICES' and  ZD.event_class_code  in ('STANDARD INVOICES', 'PREPAYMENT INVOICES', 'EXPENSE REPORTS') and...
Post a Comment
Read more