What you see
The value provided for either code combination ID or the charge account isn’t valid. (POR-2010989)
Root cause
Fusion derives the charge account with the Transaction Account Builder, using the account rules in your transaction account definition. When no rule matches this line, or a rule produces a combination that is not valid, there is no usable charge account.
How to fix it
- Note the details on the failing line: requester, purchasing category, business unit and destination type. Rules usually key on these.
- In Setup and Maintenance, open the Define Transaction Account Rules task list and find the account rule behind the requisition charge account.
- Check the rule has a condition that matches this line. A common gap is a new category or business unit the rule never mentions.
- Many setups build the charge account from the requester’s default expense account. Confirm the requester has one.
- If an account is built but rejected, check it against your cross-validation rules and confirm every segment value in it is enabled.
Where to go in Fusion
- Setup and Maintenance, Define Transaction Account Rules
- Purchase Requisitions, the line’s billing details (to see the derived account)
Sources
My Oracle Support notes, for readers with access. We do not reproduce their content.
- 2931589.1: Charge Account Can’t Be Generated For Distribution When Creating Requisition
- 2293680.1: Invalid Charge Account Error Is Returned For Specific User After Submitting A Requisition
- 2265785.1: Charge Account Error While Submitting Requisition
Sources Written in plain words from Oracle’s public documentation and the support notes and forum reports listed above. Not yet checked against a live instance by our reviewer. Navigation and behavior vary by configuration; verify in your own instance and test before acting.
Solve it, then prevent it
This page covers one issue. These help with the rest: