Just wondering after watching the MultiOrg setup videos, HOW do you set up a OU to service more than 1 LE ?
It was mentioned, however not really explained.

Thank-you
Frank

Frank,

LEs are mapped to Balancing Segment Values within a Ledger
Create multiple LEs in a single ledger.
Assign one OU to the Ledger.
This way transactions for multiple LEs are processed and accounted in a single OU.

Hasan

Thanks Hasan,

However, lets say we have 3 LE in a ledger.
We have 2 OU's
OU#1 is tied to LE#1 and LE#2
OU#2 is tied to LE#3

I thought when you define your OU, you assign it a default LE
In this case, I am not able to assign OU#1 to the GL as I have another OU#2.

Does this make any sense.. I hope so... :)

Thanks
Frank

Sorry.. I think I get it now.. all LE's are within the same GL

When I define LE#1 I will assign it Bal Seg 01 and 02
When I define LE#2 I will assign it Bal Seg 03

Then at the end, when I define my OU's
I will assign OU#1 to LE#1 = (Bal Seg : 01,02)
I will assign OU#2 to LE#2 = (Bal Seg : 03)

Is this correct ?

Thanks

Frank,

First thing first. In R12, please stop thinking in terms of a hard relationship between OU and LE.

OUs are tied to Ledgers
LEs are tied to Ledgers as well. (BSVs).

The relationship between OU and LE is derived.

Yes you assign a default legal context to OU but that does not mean that this OU is hard tied to LE.

I hope that helps.

Hasan

Thanks Hasan,

I was found this article which after reading made sense to me.
I was getting confused about "assigning a legal context" to an OU.
This is what I discovered ->

"While setting up an OU you will define a Default Legal Context, the key here is default. This is not the only Legal Entity associated with the OU that can be used on transactions within that OU it is just the default one if the derivation rules cannot find a better match."

It ALL makes sense now.. :)

Hello Hasan,

From your video on Multi Organziation Concepts
You said and displayed approx 12 minutes into the video

That OU1 will service LE1 and OU2 will service LE2

I'm a bit confused now...
I thought since BOTH LE1 and LE2 reference LEDGER#1
and BOTH OU1 and OU2 reference LEDGER#1

That OU1 will be servicing LE1 & LE2
and OU2 will also be serving LE1 & LE2

Please explain, which is correct ?
Thank-you

I did not quite get your question.
In the example both LEs (LE1 and LE2)are attached to LEDGER1.
And both OUs (OU1 and OU2)are attached to LEDGER1.
In this situation these are the possibilities.
* Both OU1 and OU2 would service LE1 and LE2
* OU1 would service one LE (LE1) and OU2 would service the other (LE2).
Relationship between OU and LE is derived. An LEs is a group of BSVs. You can restrict access of OU users on BSVs.

Thank-you Hasan,

That is what I thought.
I guess I will need to define a SECURITY rule and attach it to the PAYABLES ou responsibilities to allow only certain BSV to be processed in the example ABOVE>

Is this the recommended way of doing it ? Using Security Rules ?

Thanks again

What I'm trying to say..
Is if :
LE1 is using BSV 01
LE2 is using BSV 02
and I want OU1 to be associated indirectly with LE1
and I want OU2 to be associated indirectly with LE2
I would simply create 2 Security rules and assign them the the
2 unique responsibilites.

If I don't use SECURITY RULES, then as you said.
OU1 and OU2 will service BOTH LE1 and LE2

Correct ?

Sorry... I meant to say that when
we have 2 or more LE's that can be accessed BY 2 ou's
You need to define 2 Data Access sets and assign a different one
to each of the OU resp in order to control which BSV's that
the resp has access to...
I think this is right ?

Thank-you

Yes you can restrict an OU responsibility to use certain BSVs using either data access set (preferred method) or security rules.

Data Access Sets will not affect the BSV that is displayed in any
Accounting Key Flexfield window. That's why I need to use Security Rules.
Data Access sets will STILL display the bsv that do not relate to the ou.
Give it a try.

Thanks for the feed back.
VERY VERY MUCH APPRECIATE !!