Purchasing FAQ

Standard, Blanket, Contract, Planned

An approval group is defined which is nothing but a set of authorization rules comprised of include/exclude and amount limit criteria for the following Object Types: Document Total, Account Range, Item Range, Item Category Range, and Location that are required to approve a PO. You can always change the rules by doing the below: Navigation: Purchasing Responsibility > Setup > Approvals > Approval Groups Query the Approval group and change teh rules accordingly.

CREATE REQUISTION, RAISE RFQ(REQUEST FOR QUOTATION),QUOTATIONS,PURCHASE ORDER,RECIEPTS

Creating a Receipt with "Receipt Date" less than sysdate or today's date is referred to as 'Backdated Receipt".

No. The receipt date has to be with in open GL period.

The buffer time during which receipts can be created with out warning/error prior or later to receipt due date.

Receipt Tolerance can be set in three different places. 1. Master Item Form (Item Level) 2. setup, organization form (Organization Level) 3. Purchase Order, Receiving controls. (shipment level).

No

PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL,PO_DISTRIBUTIONS_ALL

Create PO Submit it for Approval Receive Goods against the PO (when order is delivered by the vendor) Close the PO after the invoice is created in AP and teh payments have been made to the vendor.

Approval hierarchies let you automatically route documents for approval. There are two kinds of approval hierarchies in Purchasing: position hierarchy and employee/supervisor relationships. If an employee/supervisor relationship is used, the approval routing structures are defined as you enter employees using the Enter Person window. In this case, positions are not required to be setup. If you choose to use position hierarchies, you must set up positions. Even though the position hierarchies require more initial effort to set up, they are easy to maintain and allow you to define approval routing structures that remain stable regardless of how frequently individual employees leave your organization or relocate within it.

It Depends on the setup whether it is position based or supervisor based.

A Planned PO is a long¿term agreement committing to buy items or services from a single source. You must specify tentative delivery schedules and all details for goods or services that you want to buy, including charge account, quantities, and estimated cost.

Create Requisition, Receive the goods.

If an employee/supervisor relationship is used, the approval routing structures are defined as you enter employees using the Enter Person window. In this case, positions are not required to be setup. If you choose to use position hierarchies, you must set up positions. Even though the position hierarchies require more initial effort to set up, they are easy to maintain and allow you to define approval routing structures that remain stable regardless of how frequently individual employees leave your organization or relocate within it.

Iprocurement is a self service application with a web shopping interface. WE can only create and manage requisitions and receipts. Purchasing module is form based and also lets you create PO and many other functions are possible other than requisitions and receiving.

A Blanket PO is created 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 know the detail of your delivery schedules.