Oracle Self Service Procurement Cloud: Tips on Transaction Account Builder in Requisitions
SummarySome points to note on using Transaction Account Builder in Requisitions
A common problem customers encounter and how to solve it:
User is not able to over-ride the charge account defaulted by Transaction Account Builder (TAB)
Cause: This typically happens when client is not using the seeded ‘Purchasing Charge Account rule’ and/or seeded Transaction Account Definition (TAD)
a) Client is using the seeded TAD but a custom TAB. In their custom TAB, they have changed the sequence of the account sources and ‘Requisition Charge Account’ is no longer #1 source.
Solution: Reorder the source and make sure ‘Requisition Charge Account’ is the #1 source