Weekend Learning: Introduction to technical details about SLA

While finishing up my presentation and whitepaper for COLLABORATE so I can present in April, I found the perfect article for Weekend Learning, saved a draft, and then promptly forgot to post it last night!  My consecutive posting streak is broken!  Oh well, I am going to post twice today and then know next year on February 29th that I have posted 366 days in a row!  Maybe it has something to do with my last post being the 666th post that was posted too!  Anyways, on with the show!

The MOS document "SLA: A TECHNICAL PERSPECTIVE OF THE AP TO GL RECONCILIATION" from note ID 605707.1 has a lot of good reading about how SubLedger Accounting (XLA) works with R12 so that the AP module no longer retains the accounting information.  Walk through the tables that retain all of the data, so that you can learn about the interconnections between modules that might need alerting!

Patching R12 to fix SLA and GL data

If you weren't aware, SLA (Sub Ledger Accounting) is a new feature introduced with R12 and as expected with new features is the shaking out of bugs identified by the early adopters. Not only do we find out what the possible bugs are between the SLA intermediary and the GL, but included in the article is a new note with the root cause fix as well as data fix in case data corruption has happen AND in the comments the author has given us another note which will lead us to learn more about SLA in general.