R12: Alternate Account Not In Use For Code Combinations, Still The Accounts Are Replaced By Other Combinations During GL Transfer, Why? (Doc ID 1450529.1)

Last updated on DECEMBER 21, 2016

Applies to:

Oracle General Ledger - Version 12.0.0 and later
Oracle Subledger Accounting - Version 12.0.0 and later
Information in this document applies to any platform.

Goal

Found out that during Subledger to General Ledger transfer, data gets imported properly, still some code combinations are replaced in the process with other codes.

Alternate accounts are not defined for these code combinations but further investigation shown the codes were disabled.

Is this replacement then expected?

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms