Purchase Order
Oracle Purchasing Requisition: Requisition is a document where the need for the material is specified and is raised by an employee. Types of Requisitions. 1. Internal Requisition: Transferring the material from one dept to another within the same company and not from the third party (if the reqt is fulfilled within the company) is known as Internal requisition. 2. Purchase Requisition: If we want to purchase the material from outside vendor then we raise Purchase requisition. RFQ (Request for Qutotation): The purchasing manager asks the supplier to send the quotation for the required material with the help of RFQ. Types of RFQ: 1. Standard RFQ: The normal quotation is the standard rfq. 2. Bid RFQ: It is raised when we are planning to purchase heavy material which lasts longer. 3. Catalog RFQ: When we request the supplier to send catalog of items along with the quotation then it is called as catalog rfq. Quotation: A statement of the price, terms and conditions of sale, a supplier offers us for an item or items. It is a detailed description of goods or services offered by the supplier. Types of Quotations: 1. Standard Quotation 2. Bid Quotation 3. Catalog Quotations Purchase Order: It is a statement which contains the required items, quantity, price,date when we need and the location where we need. Types of Purchase Orders: Blanket PO Contract PO Planned PO Standard PO Standard PO: It is used for only one time purchase of various items when we know the details of goods or services we require, estimated cost, qty, delivery schedules and accounting distributions. Blanket PO: It is raised when we know the details of goods or services that we plan to buy from a specific supplier in a period, but we don’t know the details of delivery schedules. Contract PO: Here we don’t know any information regarding items but just know the terms and conditions. Planned PO: A planned po is along term agreement committing to by items or services from a single source. Here we know all the details. Main concepts in PO: Ø Item details o Defining item category and its segment values o Registering the item category. o Define category sets and item. Ø Employee o Defining job and position of the employee o Defining employee and his approval limits o Defining the employees as buyers § Define and assign the approval groups to the employees Ø Supplier o Define and approve the supplier o Define the supplier list : Flow of Purchase Order Ø Raise the requisition. Ø Check whether the requisition is approved or not. Ø Raise RFQ. Ø Raise the quotation. Ø Raise the purchase order. Ø Receipts Ø Inspect the goods Matching approval levels: 2-Way Matching Invoice à P.O. Invoice à Receipts 3-Way Matching Invoice-à P.O. Invoice à Receipts Invoiceà Invoice 4-Way Matching Invoice-à P.O. Invoice à Receipts Invoiceà Invoice Invoice à Inspect 1)PO_HEADERS_INTERFACE Interface Tables:PO Tables And Details
Important Table in Purchasing Module of Oracle apps
=========================================
Purchase Order
Po_headers_all
Po_lines_all
Po_line_locations_all
Po_distributions_all
Buyers
Po_agents
Document and line types
Po_document_types_all_b
Po_line_types_b
Releases
Po_realeases_all
Requisitions
Po_requisition_headers_all
Po_requisition_lines_all
Po_req_distributions_all
Vendors
Po_vendors
Po_vendor_sites_all
Po_vendor_contacts
Receiving
Rcv_transactions
Others
Mtl_system_items_b
Mtl_categories_b
Links between Oracle Apps PO Tables
============================
Po_headers_all/Po_lines_all --> po_header_id/po_header_id
Po_headers_all/Po_vendor_sites_all --> vendor_site_id/vendor_site_id
Po_headers_all/Po_vendors --> vendor_id/vendor_id
Po_headers_all/Po_line_locations_all--> po_header_id/po_header_id
Po_lines_all/Po_line_locations_all --> po_line_id/po_line_id
Po_lines_all/mtl_system_items_b --> item_id /inventory_item_id ( get for master org)
Po_lines_all/Mtl_categories_b --> category_id/ category_id
Po_line_locations_all/Rcv_transactions -->line_location_id/po_line_location_id
Po_vendor_sites_all/Po_vendors --> vendor_id/ vendor_id
po_distributions_all/po_req_distributions_all --> req_distribution_id/distribution_idPO Interface Tables Details
====================
1)DOCUMENT_TYPE_CODE = This column will accept any of the following string.
STANDARD
BLANKET
PLANNED CONTRACT
2)VENDOR_NAME =It will accept valid vendor name . by using PO_VENDORS Table
we can findout wether vendorname is valid or not.
4)VENDOR_SITE_NAME = PO_VENDOR_SITES_ALL
5)VENDOR_CONTACT_NAME = PO_VENDOR_CONTACTS
6)SHIPTO = HR_LOCATIONS table will be use to find the location is valid
or not.
7)BILLTO = HR_LOCATIONS table will be use to find the location is valid
or not.
8)CREATION_DATE =It should be in the Date Format.And also <=SYSDATE
9)AGENT_ID = it should be valid agentID(Buyer ID) .By using PO_AGENTS table
we can find out wether agent_id is valid or not.
10)ORG_ID =It should be Valid OrgID. By using hr_operating_units table we
can find wether it is valid or not.
11)AUTHORIZATION_STATUS = Valid status either APPROVED,INCOMPLETE,CANCELLED
12)CURRENCY_CODE = Valid Currency Code from FND_CURRENCIES table
we can find wether valid currency code or not.
PO_LINES_INTERFACE:
====================
LINE_NUM = Will accept only unique values.
LINE_TYPE = Should be a Valid Line type. By using PO_LINE_TYPES we can findout
wether it is valid or not.
ITEM =It should be a valid Item by using MTL_SYSTEM_ITEMS_B table we can
find wether valid Item or not.
ItemDesc = Item Desc also should be valid description
UOM_Code =Should be valid UOM by using MTL_UNITS_OF_MEASURES table we can find
wether it is valid or not.
QUANTItY =Will accept any Positive Number
unit_Price = Will accept any Positive Number
NEED_BY_DATE = date Format and >= PO creation Date(from PO Headers Interface table)
PROMISED_DATE = date Format and >= PO creation Date(from PO Headers Interface table)
ORG_ID =It should be Valid OrgID. By using hr_operating_units table we
can find wether it is valid or not.
SHIP_TO_ORG =Valid ORg_ID
ShipTo_Loc = Valid Shiping Location
PO_REQUISITION_INTERFACE_ALL
PO_REQ_DIST_INTERFACE_ALL
PO_HEADERS_INTERFACE
PO_LINES_INTERFACE
PO_DISTRIBUTIONS_INTERFACE
AP_SUPPLIERS_INT
AP_SUPPLIER_SITES_INT
AP_SUP_SITE_CONTACT_INT
RCV_HEADERS_INTERFACE
RCV_TRANSACTIONS_INTERFACE
Error Table:
PO_INTERFACE_ERRORSQuery to list canceled Requisition:
select prh.REQUISITION_HEADER_ID,
prh.PREPARER_ID ,
prh.SEGMENT1 "REQ NUM",
trunc(prh.CREATION_DATE),
prh.DESCRIPTION,
prh.NOTE_TO_AUTHORIZER
from apps.Po_Requisition_headers_all prh,
apps.po_action_history pah
where Action_code='CANCEL'
and pah.object_type_code='REQUISITION'
and pah.object_id=prh.REQUISITION_HEADER_ID
0 comments:
Post a Comment