This content has been marked as final. Show 5 replies
There is no PO preparer as such.1 person found this helpful
A preparer exists on the requisition.
You can consider using po_distributions to jump to the po_req_distributions and then finding the preparer for that requisition.
There is no "owner" of a PO unless you want to treat the buyer as the owner.
Hope this helps,
If that's the case, then what does 'can owner approve the PO?' workflow process is meant for?
I'm now really confused on this process.
Who's the owner that it is being referred to ?
Owner can approve - Allow document owners(Buyers) to approve the documents they create.
Here Owner refers to the Buyer who creates the PO
Edited by: user12558002 on Jul 28, 2011 6:19 AM
Here, I don't see if it really is referring to the buyer .
The agent ID for that particular PO is different from the owner (the workflow attribute preparer_id is being referred to owner here ).
My question is who can be the preparer if the purchase requisition for the PO is being prepared from iProcurement and PO is automatically created with AUTOCREATE workflow without buyer intervention?
Your question is : Who can be the preparer if the purchase requisition for the PO is being prepared from iProcurement and PO is automatically created with AUTOCREATE workflow without buyer intervention?
Ans : a) When you create a requisition using iProcurement (catalog requisition), you normally search items under shop which are linked to BPAs. When requisition is approved and a standard PO is auto created and auto approved then the Std PO carries the buyer name of the BPA which was used during requisition creation.
b) For non-catalog request (requisition)/smartform it refer the CPA of the buyer while creating a std PO.
Earlier you asked : how do I find the requestor and preparer/owner of the PO? How do these values get populated?
Ans : Sandeep has said it correctly that in PO, there is no concept of requester/preparer etc.. Buyer of the PO will be treated as requestor and preparer/owner of the PO. This value is populated as mentioned above in point a).