My Oracle Support Banner

R12: Liability Account is NULL for Debit and Credit Memos From a Return to Vendor (RTV) (Doc ID 2428664.1)

Last updated on FEBRUARY 27, 2019

Applies to:

Oracle Payables - Version 12.0.6 and later
Information in this document applies to any platform.

Symptoms

This issue occurs in Applications Release version 12.0.6 and higher.


There is no Supplier Site Liability Account on Debit Memos that are created using the Return to Vendor (RTV) process. The system is setup to derive the
Liability from the OU Profile Options defined. This is the desired setup and it works for all transactions except Debit and Credit Memos from RTV
transactions.

There is a progression for defaulting the liability accounting. The liability account is either selected from the supplier Site, Third Party site, or
Operating Unit (OU).  

For RTV Debit Memos, when there is no liability account value at the supplier site, it is not using the value defined at the OU.  


The following error is returned during the accounting process for these credit/debit memo invoices:

95353  Subledger Accounting was unable to derive an accounting code combination using the account  derivation rule Liability Account owned by Oracle.
Please review the account derivation rule and make sure it derives a valid accounting flexfield combination for the source values passed for the transaction.


 

Changes

 

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.