Thank you for supporting the Cloud Customer Connect Community in 2024. It's a gift to work with you!

Look back
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Oracle Self Service Procurement Cloud: Tips on Transaction Account Builder in Requisitions

edited Mar 30, 2018 1:31AM in Self Service Procurement

Summary

Some points to note on using Transaction Account Builder in Requisitions

Content

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)

Scenarios: 

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

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!