Skip to main content

What is Difference Between Complex Purchase Order and Standard Purchase Order?


Oracle Services Procurement – Complex Purchase Orders – Oracle Services Procurement is part of Oracle Advanced Procurement Suite and provides state-of-the-art functionalities to strategically procure services that deals with various procurement aspects such as Prepayment, Retainage etc. In addition to the Temporary Labor Procurement functionality, Oracle Services Procurement helps us to significantly improve the Lumpsum and Milestone type procurement activities through Complex Purchase Orders.


Following Points to be noted in relation to Complex Purchase Orders:

• Complex Purchase Orders can be created, updated and viewed using Buyer Work Centre only.
• The Schedules/Shipments for the standard purchase orders is called as “Pay Items” in the complex purchase orders.
• There are 3 types of Pay Items available in the complex purchase orders as – Milestone, Lumpsum and Rate. Availability of the pay items for selection in the buyer work center depends on the line type and document style setups.
All line types that are configured with “Fixed Price” value basis will have all types of Pay Items available for selection.
• Line types with “Quantity” value basis will have only the “Milestone” Pay Items available for selection.
• It is received through work confirmations and not through standard PO receipt process.
• Partial completion of Milestone Pay Items is not allowed while creating work confirmation but the same is allowed for Lumpsum and Rate Pay Items.
• Progress Payment can be made using milestone type complex purchase orders.
• Retainage and advanced payment can be handled using complex purchase orders.
• Work Confirmations can be created using Oracle iProcurement, iSupplier or Buyer Work Centre.
• Work Confirmation approval mechanism uses Oracle Approval Management Engine (AME).

Required Setups:

Enable Services Procurement:
Once you have purchased the licenses of Oracle Services Procurement module, please setup the “PO: Enable Services Procurement” profile option to “Yes” at the site level.

Document Style Setup:
Responsibility: Purchasing Superuser or similar
Navigation: Setup -> Purchasing -> Document Styles
You will find seeded complex purchase order styles in the Document Style page.
Click on the Update icon to update the style definition as appropriate.
In this setup, you will be able to enable/disable the document types, commodities, pay items and progress payment options for the complex respective complex style.

Line Type Setup: 
Responsibility: Purchasing Superuser or similar
Navigation: Setup -> Purchasing -> Line Types
You will find all the seeded line types here but in case you need to define a custom line type to be used for complex purchase orders, please note that, all the “Fixed Price” Value Basis line types will be able to use Milestone, Lumpsum and Rate Pay Items while the “Quantity” Value Basis line types will be able to access “Milestone” Pay Items only.

The main difference between complex PO and standard PO is:
1) Complex PO can have Milestone, Lumpsum and Rate but not standard PO
2) Complex Purchase Orders can be created, updated and viewed using Buyer Work Center only.

However standard PO can be created, updated and viewed in both BWC and PO forms.

Also, We generally create standard purchase orders for one-time purchase of various items. We create standard purchase orders when we know the details of the goods or services we require, estimated costs, quantities, delivery schedules, and accounting distributions. If we use encumbrance accounting, the purchase order may be encumbered since the required information is known.

 

Comments

Popular posts from this blog

SQL Query to extract Oracle Purchase Order Information

SELECT   poh.po_header_id,    poh.type_lookup_code PO_TYPE,   poh.authorization_status PO_STATUS,   poh.segment1 PO_NUMBER,   pov.vendor_name SUPPLIER_NAME,   povs.vendor_site_code Location,   hrls.location_code Ship_To,   hrlb.location_code Bill_to,   pol.line_num ,   msib.segment1 Item,   pol.unit_price,   pol.quantity,   pod.amount_billed Amount,   pod.destination_subinventory,   ppf.full_name Buyer_Name,   poh.closed_Code  FROM   PO_HEADERS_ALL poh,   PO_LINES_ALL pol,   mtl_system_items_b msib,   PO_LINE_LOCATIONS_ALL poll,   PO_DISTRIBUTIONS_ALL pod,   po_vendors pov,   po_vendor_sites_All povs,   hr_locations_all hrls,   hr_locations_all hrlb,   per_all_people_f ppf,   po_line_types polt WHERE   1                         =1 AND polt.line...

Query to find Operating Unit, Business Group and Legal Entity Information

SELECT   DISTINCT   hrl . country ,                  hroutl_bg . name              bg ,                  hroutl_bg . organization_id ,                  lep . legal_entity_id ,                  lep . name                    legal_entity ,                  hroutl_ou . name              ou_name ,               ...

How To Enable / Disable Forms Personalization Option

Forms Personalization gives great flexibility to execute custom business logic without performing so much of technical work. To start forms personalization navigate to Help -> Diagnostics -> Custom Code -> Personalize But many time when we click on personalize it give below error  " Function is not available for this respnosibility. Change responsibilities or contact your System Administrator " To Enable access to forms personalization function we need to set below profile option.  -  Utilities:Diagnostics -> Yes / No It determines the diagnostics option is enabled for a user / responsibility or site, depending on the level profile option is set. Navigate to System Administrator -> Profile -> System Query for your user / responsibility for which you want to provide access. Set the value to 'Yes' , If you want allow access to forms personalization Since we change the profile option please change the respons...