We are on APP10 UPD 9. Recently we had a testing on Purchase Order Authorization Rule for project, and seems like it does not working. below PO line is inherited from project PR, and it does have project connected on the PO line, but when it is being released, the expected PO rule is not fetched. below PO rule DEREG is the expected rule.
Does anyone has experience on this? is this a bug?
Page 1 / 1
Hi Ron,
it looks like you do not have Project Unique Procurement setup in the project, because the Project ID does not get filled in the PO header.
This is where that is set on the project
The logic is: If project Unique Procurement is OFF, the PO can contain PO Lines from multiple projects, thus the system cannot find Project specific PO Authorization rules (as the rule might be different for the different PO lines.)
In short “ If Project Unique Procurement is OFF, project specific PO Authorization rules do not work, neither do Project Roles in the Routing Template”
Project specific PR Authorization is possible, as that is done per PR Line
If you turn Project Unique Procurement on, and create a new PO, it should work.
Hope this helps
Regards Erik
@EriLNL Really make sense to me. Thank you very much.
@EriLNL Thank you for your reply.
Another question, apart from inherited from project, there is no way to connect the project to the purchase order on purchase order header.
in other words, if i am trying to connect the project on the purchase order header where the project id is missing from the header, there is no RMB function to make it happen, correct?
Thank you.
@EriLNL Thank you for your reply.
Another question, apart from inherited from project, there is no way to connect the project to the purchase order on purchase order header.
in other words, if i am trying to connect the project on the purchase order header where the project id is missing from the header, there is no RMB function to make it happen, correct?
Thank you.
@ronhu Can you use the List of Values in this Project ID field?