Hi Hasan,

Multiple companies with the same 4Cs can be put in one ledger, or in different ledgers to segregate data so that users logging in to one ledger cannot see data sitting in another ledger. Those are the different scenarios implemented in the Oracle GL.

I think that even if all the companies with the same 4Cs are put in the same ledger, users logging into one company cannot see data sitting in another company unless they are given privileges to do so.

My point is that data segregation can also be achieved using Restricted Data Access Set or Security Rules or a combination of both. So, why is it an option to put companies with the same 4Cs in different ledgers just to achieve Data Segregation? I think that even with Data Segregation between groups of users in mind, all the companies with the same 4Cs should be put in a single ledger, and then we implement Restricted Data Access Set or Security Rules or a combination of both.

My point, in a nutshell, is that companies with same 4Cs should not be put in different ledgers just for the purpose of Data Segregation groups of users.

I do, however, understand that companies with different 4Cs have to be put in the same ledger.

Please, clarify this notion and give examples if possible.
Thank you a lot.

You are right. No clarification needed here.
If you have four companies sharing 4Cs and they all are ok with the same ledger options, you can put them in one ledger.

Yes... Interesting Hasan,

The key is Ledger options might need to be different and hence separate ledgers could be the way to go.
If ledger options are the same, then keep them all in 1 ledger.

Thanks

Charlie,
What do you call "Ledger Options", here? You are confusing me now. Oh, I see, you are trying to say, 4Cs. Ok!

Ledger Options = Accounting Setup that you specify on create ledger screen like number of future enterable periods, retained earning accounts, rate type, suspense account, etc etc.

Even if two companies share the same Cs and they want to use different retained earnings accounts or different number of future enterable periods, they would go in two separate ledgers.

Hasan, thank you for the clarification.

I was finding it difficult to formulate my initial question. Let me now put it this way.
In subledgers, I understand the concept of data segregation, hence, Operating Units, and can give an example of data segregation as Supplier Site data which is different for each Operating Unit within an Oracle instance.

Could I cite ledger options as the reasons for data segregation in Oracle General Ledger, when two companies with the same 4Cs are dumped in separate ledgers?

Or, are there other data which we try to segregate when we put two companies with the same 4Cs in separate ledgers? What data we are trying to separate?
I hope you understand my question! Thanks.

I am trying to understand the question but I guess I am not really there yet. Let me try to answer your granular questions. Hopefully that will fill the gaps for you in the broader picture that you have in your mind.
You asked "What data we are trying to separate?". GL data would include journals and balances.
Also understand that this is a logical separation not physical. The data for all ledgers reside in the same back-end database tables. However one group of users can only see restricted data (say for one company) from the front-end.
You asked "Why would we dump two companies with the same 4Cs in separate ledgers?". Mainly because they want to use different ledger options.
The data is segregated in GL at ledger level i.e. if you are connected to one ledger you cannot see the data in the other ledger (unless you put both ledger in one Data Access Set). Also note that you can even also separate data within one ledger from users by companies (or by other segments) using Data Access Set/Security Rules. That is why we can put 2 companies sharing the Cs and ledger options in one ledger and yet the end-users of the two companies will not really notice that their ledger is shared with another company.

I hope that clarifies some points for you.

Definitely, Yes! Thank you, Hasan.