Oracle Apps Different Types of Purchase Order

A Standard Purchase Order is one time purchasing to buy goods or services.You can create PO when you know the Item, Price, Delivery schedule and Payment terms

A Blanket Purchase Agreement it’s a long time agreement where you don’t know about Quantity, Price and required Delivery schedule. The Quantity and Price fields will be disabled when you make Blanket Purchase Agreement. You have to enter a Price. The required Quantity, Delivery Schedule and final Price will be informed to the Supplier by creating Blanket Releases against the Blanket Purchase Agreement.

A Planned Purchase Order it’s a long time agreement where you are not sure about the required delivery schedules. You know the details like Item, Price, Delivery Schedule and Payment Terms. In the Planned purchase order you have to enter a Need-By date, but this date that you enter will be treated only as a tentative date. The exact date on which the shipments are to be delivered is informed to the Supplier by creating Schedule Releases against the Planned purchase order.

A  Contract Purchase Agreement is document which gives standard term and conditions created. You do not know even the item that is to be purchased. The only information that you provide in a Contract Purchase Agreement is Supplier, Supplier Site, Payment Terms and Agreement Control details. Standard Purchase Orders are created by referring to the Contract Purchase Agreement when something is to be purchased against this Contract Purchase Agreement.

Internet Procurement interview question and answer

Que:-What is iProcurement?

Ans:-   iProcurement is a self-service web Purchasing application. Consider it as an alternate application for creating purchase requisitions and simple receiving.

Que:-  : What is a punchout?
Ans :-    : Punchout enables buyers to click a link that goes to a supplier’s catalog, search for

items on the supplier’s site, and return those items directly to the buyer’s shopping

cart.

Que:-  : Is POR_CUSTOM_PKG redundant in 11.5.10 ?
Ans :-    : Not really, it is still used. However rebuild of account functionality was moved to OAF from por_custom_pkg in 11.5.10

Que:-  : Do we create purchase orders in iProcurement ?
Ans :-    : No, you can create requisitions in iProcurement.

Que:-  : If a requisition has been approved in iProc, we want such requisitions to be Auto-Approved once they get converted to PO. How do we facilitate this?
Ans :-   : In Workflow "PO Create Documents", assign a default value Y to attribute "Is Automati Approval Allowed?".

Que:-  : We need to submit PO Creation as soon as the Requisition gets submitted & auto-approved in iProc. How can we do it?
Ans :-    : In Workflow "PO Requisition Approval", The item attribute “SEND_CREATEPO_TO_BACKGROUND” needs to be assigned value of N.
This will enable Real-Time processing of requisition mainly because the user can get a PO Number within the same browser session if auto-approval is enabled.

Que:-  : What are the key advantages of punchout over local catalog management?
Ans :-    : 
A. You do not need to maintain the pricing information of items. Supplier will publish their latest pricing details in their iStore.
B. You do not need to upload the items of your supplier into your system.
C. The up-to-date stock level information is made available on Suppliers Website.

Que:-  : When shopping basket is brought back from suppliers website after punchout, how does the item category code of supplier item get mapped to the category code in Oracle?
Ans :-    : Suppliers punchout basket will always contained universally recognized category codes i.e. UNSPSC codes. You will need to define the mapping for each such expected code in eCommerce gateway. These will be mapped to your inventory category codes (the good old mtl_categories ).

Que:-  : After the purchase order gets approved, you wish to send Purchase Order electronically to the supplier. Which XML document format is used?
Ans :-    : "PO 007" is the OAG format that is used for electronically sending XML Purchase Order to supplier.

Que:-  : Have you done any customization in Oracle iProcuremnt?
Ans :-    : All the implementations of iProcurement will involve customization of workflows to some extent.
Customization to Account Generator workflow is a must for any iProc implementation. 

Que:-  : What is the advantage of punching out via exchange, rather than punching out directly to suppliers website?
Ans :-    : If you enable punchout via Oracle Exchange Server, you will then have to open up your company firewall just for the exchange server. However if you decide to enable a direct punchout, you must open firewall for Suppliers server.

Que:-  : Give me some example of personalization’s done to Oracle iProcurement.
Ans :-    : 
a. Change the Branding Logo.
b. Add Purchasing News and Purchasing Policies
c. Removed field “New Supplier” from iProc Supplier Region

Que:-  : You wish to customize the Purchase Order header in the XML file that gets sent to supplier. How will you do it ?
Ans :-   : Two options:-
 a. Modify the XML Message Map for PO-007 using XML Gateway Developer.
 b. Customize view PO_ECX_HEADER_ARCH_V(prior to 11.5.10) or customize view ITG_PO_HEADER_ARCH_V(11.5.10 onwards)