However you never ever use that approach in real life for modules such as Oracle Payables, Oracle Receivables, Oracle Cash Management, Oracle Fixed Assets or Oracle Project Accounting etc. The reason is that, SLA comes pre-configured for all the widely used modules in the EBusiness Suite. All the commonly used rules are already seeded into the SLA config by Oracle, hence all you need to do is to customize those components.
Before we see the steps for customization of SLA, let us first do some questions and answers
Question - I can customize the account generator in Procurement and Fixed Assets. Do I really ever need to customize “Subledger Accounting” in such cases?
Answer- The pre-configured SLA by Oracle will use the accounts generated in respective modules as the source. The seeded ADR's will in most cases return the very same accounts that are generated in the respective modules. Effectively "garbage in garbage out", or you can say "quality of the account that goes into SLA, and the same quality accounts are then sent to General Ledger". The message from seeded SLA in most cases is “What you feed to SLA will also be fed into the Oracle General Ledger”. Therefore if you have already customized the account generation workflow in the respective module then you do not require customization in SLA. In fact, the customizations on the seeded SLA configurations must be kept to bare minimum. Although SLA provides you with ability to override accounting definition, however the main reason for creation of SLA was to implement multiple shadow accountings against ledgers.
Question - If all the respective modules can generate accounting properly then why is SLA really needed?
Answer - Well, the main reason behind creation of SLA itself was to create shadow journals for secondary ledger. Please see the Part 1 in this series of articles.
Now let us take the example for customization of an existing SLA definition pre-seeded by Oracle in R12. In this example, a SLAM named STANDARD_ACCRUAL is attached to the Ledger [Set Of Book equivalent of 11i ]. As you will notice from the image below, many modules such as Leasing, Loans, Cash Management, Payables etc are attached to this SLAM. However we are interested in modifying just the Payables piece of this SLAM. Create a copy of this SLAM as shown in the image below. We will create a SLAM named ANIL_SLAM__STANDARD_ACCRUAL which happens to be the exact copy of SLAM named STANDARD_ACCRUAL.
Now create new entry for Payables within the copied SLAM, i.e. new SLAM will
be " ANIL_SLAM__STANDARD_ACCRUAL"
Now you have created a new SLAM. In this SLAM, end date the AAD assignment of Payables and add a new entry for Payables. Note that we still have AAD named "Accrual Basis" attached. However after we copy the "Accrual Basis" into a custom AAD, we will then return to this screen in order to replace "Accrual Basis" by custom AAD. Click on "Application Accounting Definition" button.
Now, click on copy, and this time we will copy the AAD definition named “Accrual Basis” to create a new AAD named ANIL_STD_PAYABLES_STD.
The new AAD will be called ANIL_STD_PAYABLES_STD as shown below. Click on button labelled Done to complete the Copy operation for the AAD.
Now this new AAD has been created. Before we customize this AAD, we need to ensure that this AAD has been attached to the custom SLAM that we created in Step 1 of this article.
Now, back to the SLAM screen, for the custom SLAM, for Payables AAD assignment record, we attach the custom AAD to Payables. Please note that the Payables entry that is attached to custom AAD named “Accrual Basis” has now been end dated, as shown in image below.
Now go back to AAD, by clicking on Application Accounting Definition button as per the image above.
Follow the instructions as per images below
Now copy the Journal Line Definition itself.
The image below shows how the custom/copied journal line definition will be modified. Our idea here is to attach a custom ADR for the generation of an account.
The name of the copied JLD will appear as below.
Attach the custom ADR as shown below
And now attach your custom Journal Line Definition to the custom AAD.
This completes the cycle for customization of the pre-seeded SLA configuration.