New Profile Option "SLA: Disable Journal Import"

SLA: Disable Journal Import
======================

Today i am going to talk about this profile option "SLA: Disable Journal Import".

There has been many changes (Functional as well as Technical) in Release 12 majority of them
were because of Subledger accounting. This is one of the notable feature.

In earlier versions (11x), whenever there is a transfer of entries made from Subledger to General ledger, it used to happen through in steps, as stated below:

Step 1 - Run Transfer to GL program from Subledger
Step 2 - Data will be transferred from Subledger to GL interface table
Step 3 - Run Journal import from General Ledger which will import the journals from
GL interface table to GL base tables.
Step 4 - Query the batches and then post the journals imported.

In Release 12, most of the above mentioned steps remains the same, apart from STEP 2.
That is, by default, when you run the Transfer to GL program, it also performs the Automatic Journal import program along with it, which results in no data lying in GL Interface Program.

It is a new feature, what is wrong in it ?
=============================
The reason why the interface tables are populated before hitting the base tables are to make
corrections or rollback the mistakes. All necessary corrections are carried out in interface tables
and only the CORRECT data is sent to General Ledger. Due to this new standard feature, one
cannot see any data in the interface table, because data does not stay in interface table.

How to overcome it?
================
By setting the profile option "SLA: Disable Journal Import" to YES, we are directing the system not to perform the journal import automatically. So the journal import has to be triggerred Manually, which means the data will stay in the interface table.
The default value for the profile option SLA: Disable Journal Import is NO, which means when ever a data is sent to General ledger , the subledger tables alone are used (i.e. tables with prefix XLA).

At what level the profile option can be changed ?
=====================================
The "SLA: Disable Journal Import" is not updatable at User,Responsibility and Application level. It can be updated only at SITE level.

What happens when a Journal Import fails?
=================================
When the journal import fails and the profile option SLA: Disable Journal Import was set to NO, the data will not stay in the GL interface tables, the data will be rolledback to the subledger tables.

By setting the SLA: Disable Journal Import to YES is there any Problem ?
=======================================================
YESSSSSSSSSSSS
1) The structure of R12 is designed such a way to avoid or reduce the reconciliation worries. When you set this profile option to YES, and make corrections if any and then transfer the DATA to GL, the data available in GL and data available in Subledger becomes OUT OF SYNC.

2) Also this profile option is set only at Site level, which means it applies to the whole environment, and not specific to an Application or an User.

So, what are oracle recommendations about this profile option:
================================================
1) By default the value of this profile option is NO
2) If user has AP/AR , but not oracle GL, they should set SLA: Disable Journal Import=Yes
3) If user has AP/ AR as well as oracle GL, they should set this profile to No to ensure the data in SLA and GL are in sync
4) If the profile options stays at the default value from the start of the implementation , please DO NOT change it.

Hope this adds to your knowledge kit.
Have a good Day ... !