R12: AP: Different Liability Account For Payment Request Invoice Than For Other Invoices
(Doc ID 2304459.1)
Last updated on JULY 11, 2024
Applies to:
Oracle Payables - Version 12.0.6 and laterInformation in this document applies to any platform.
Symptoms
On : 12.1.3 version, Accounting Issues in AP
ACTUAL BEHAVIOR
---------------
The problem is that the Liability account defaulted on the “Payment request” is the liability account defined in Financial Options and cannot be modified as the Invoice is created in Validated status.
This account is “a Third Party Controled” account.
That means, as the party is not identified on the invoice Header (Supplier Number is Null), when Create Accounting is run, the system fails with the message "The account code combination xxx for line x is a control account
EXPECTED BEHAVIOR
-----------------------
Expect to be able to custom Liability account for Payment request invoices, to be different from other invoices
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Payables Manager
2. Setup > Accounting Setups > Subledger Accounting Setup > Accounting Methods Builder > Methods and Definitions > Journal Line Definition > Journal Line Type
3. Assign Custom Account derivation rule
Changes
Custom Account derivation rule for Liability, Basic Journal Line type to met the different account for:
- Payment request invoices
- Other invoices
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |