How To Use SLA To Override Accounting created by AutoAccounting
(Doc ID 834475.1)
Last updated on SEPTEMBER 19, 2017
Applies to:Oracle Receivables - Version 12.0.0 and later
Information in this document applies to any platform.
Review the setup for replacing the accounting generated by AutoAccounting using Subledger Accounting (SLA) in R12.
In Release 11i AutoAccounting controlled all the derivation of code combinations. Based on what you setup in AutoAccounting, the accounting code combinations were derived from limited sources like transaction type, customer site or a fixed value. There was no flexibility to source accounting combinations from any other source. For example if you had an invoice with two lines, AutoAccounting would always give the same account for both the transaction lines, unless they were for different items.
In Release 12, for the same case we can replace the accounting derived by AutoAccounting for one of the revenue lines with a different value.
We will use the following examples to understand the flexibility provided by SLA:
- Replace the accounting code combination for negative revenue lines with a fixed code combination.
- Replace the accounting code combination for freight lines based on the value entered in Transaction Information Descriptive Flexfield (DFF).
- Replace the Cost Center on the Accounting Code Combination for Exchange Gain / Loss Account based on the Receivable Account on Transaction Type or Cash Account on Remittance Bank.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!