A solution to an existing issue, a new hassle for future; Implementing Subledger Accounting (SLA)
Accounting for all transactions uses Subledger Accounting (SLA) architecture which is an enhancement of the standard accounting process, and contains changes to the overall process flow, user interfaces, and some programs. SLA architecture delivers many benefits, and lets you customize the way accounting is performed for a specific event. You can use accounts derived from custom business logic based on data provided by the application (accounting sources).
SLA is a common rule-based accounting engine used by Oracle products that posts accounting entries into Oracle General Ledger. Rules are user defined, and reside in a common repository for all subledger applications such as Oracle Cost Management. The SLA accounting engine is also a common engine for all subledger applications and provides you with a single common paradigm for defining your accounting behaviors.
The subledger accounting engine lets the accounting department maintain sophisticated control over accounting and charts of accounts. Accounting rules can be defined against most attributes. For example, you can use an attribute of an item to redirect accounting to the proper category of Cost of Goods Sold within the Chart of Accounts. You can also control and avoid user errors from being entered into the application. Incorrect entries can be redirected to proper accounts.
But it comes with challenges. We honestly know that we have to extend it. But we have to this in a way that;
- We should not have to create code for each custom rule. It kills the efficiently especially if you have long deployment windows
- It should be plug & play by simple and standard configuration
- It should use existing framework for logging and monitoring
- It has to be fast, so not become a bottleneck in Create Accounting programs.
We have created a ready-to-deploy framework for SLA extensions and Import/Export functions that enables a really fast start and saves more than 100 days of development and testing.
We have demonstrated this also in Oracle Collaborate 15-16 and each were about 200+ users sessions with a full room.