Вы находитесь на странице: 1из 6

Question : What is a punchout?

Answer : This is a mechanism by which buyers can navigate to Suppliers website straight from iProcurement. Once
the shopping is finished, they then checkout the basket on suppliers website itself following which the shopping
basket is brought back to iProcurement. Shopping basket is nothing but a returned XML file that contains the
list/quantity/price of items checked out from suppliers website.

Questions : Do we create purchase orders in iProcurement ?
Answer : No, you create requisitions in iProcurement.

Question : We need to submit PO Creation as soon as the Requisition gets submitted & auto-approved in iProc. How
can we do it?
Answer : 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.


Questions : What are the key advantages of punchout over local catalog management?
Answer :
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.

Question : 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?
Answer : 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 ).



Question : Have you done any customization in Oracle iProcuremnt?
Answer : Note: 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.
You may visit the article Oracle Account Generator Workflow Example to learn steps for customizations of Account
Generation workflow in Oracle Apps.

Question : What is the advantage of punching out via exchange, rather than punching out directly to suppliers
website?
Answer : 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.

Question : 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?
Answer: In Workflow "PO Create Documents", assign a default value Y to attribute "Is Automatic Approval Allowed?".


Question : Give me some example of personalizations done to Oracle iProcurement.
Answer :
a. Change the Branding Logo.
b. Add Purchasing News and Purchasing Policies
c. Removed field New Supplier from iProc Supplier Region


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












This is not a comprehensive BR100, but this article will give you an outline of the steps to
implement Oracle iProcurement using Punchouts.
I will try to cover as many steps for full cycle iProcurement implementation using Punchouts.
This is due to email requests & the comment requests that I received to write something on
iProcurement implementation.
What is a punchout?
In your iProcurement homepage, your suppliers can raise requisition to buy items like stationary.
By punchout, we integrate iProcurement with Suppliers website. From a users perspective below
steps take place:-
1. Buyer logs into iProcurement Homepage
2. Buyer then sees various suppliers for which punchouts are enabled [depending on their
security via realm & secured attributes]
3. Buyer clicks on a stationary supplier and browser displays suppliers website.
4. Buyer selects the items on supplier website and adds them to his cart.
5. Buyer checks out the basket from Suppliers iStore [website]
6. The items selected are brought in as Shopping Basket in iProcurement
7. Requisition is created in iProcurement and sent for Approval [can be auto approved].


Typical iProcurement Steps [assuming no encumbrances setup]
a. Create Requisition
b. Approve Requisition
c. Auto-create & auto-approve Purchase Orders for approved requisitions.
d. Send PO XML to Supplier [if approver is setup as trading partner for XML PO]
e. Create receipts for goods [optional depending on setup]
-----Other non iProc steps----
f. Supplier sends Invoice electronically [posts to your XML Gateway electronically]
g. Invoice is Matched, Approved & Paid
Account Generation for iProcurement Requisition
Decide the rules for your account generation. For this you will need to customize PO Requisition
Account Generator. For details of account generator implementation visit link Account Generation
using Workflow .
You may also visit Rebuilding Generated Account in iProcurement 11.5.10 using OA Framework


PO Create Documents Workflow
In iProc you create Requisitions, which then get converted to a Purchase Order using workflow
PO Create Documents .
In this workflow, you must examine & modify the default values of following attributes[sample
defaults values listed below]:-
Is Automatic Creation Allowed -- Y
Should PO be created from iProc requisition without user intervention.
Is Automatic Approval Allowed Y
Should Contract be used to auto create Doc Y
Should non-catalog request be auto sourced from contract Y
Is Contract Required on Requisition Line N
There could be other attributes of your interest, but my implementation involved usage of
contracts to create Purchase Orders. We have a blanket contract against each iProc supplier. The
values above for those attributes are merely indicative of one scenario.

PO Requisition Approval Workflow
Similarly for workflow PO Requisition Approval, assign a default value for attribute
Send PO Auto-creation to Background N









Punchout Catalog



Store

Оценить