By using this website, you agree to our Terms of Use (click here)
We have some accounts that must not use default segment values for some segments and other segments should only be default.
I've tried following the user manual on this setting it up on GL Account Access. I can't get it to work. User guide says this:
If you are using restriction groups to control the accounts and subaccounts that can be used together, you must create at least two groups and include all subaccounts in either of the groups. For example, suppose that you need to restrict visibility of subaccounts for only one account. To solve this task, you create two restriction groups. In the first group with direct restriction, you include a GL account and the list of subaccounts that should be related to this account. In the second group with inverse restriction, you include the same account and subaccounts that should not be displayed after users select this account. As a result, when users select the account on a form, they will see only one of the subaccounts included in the first group.
As soon as i add an account to one Group, it cannot be added to a second group. Any idea?
Ok so I thought I had sussed this out from the Advanced System Management training and came up with a few groups of account/subaccount (segment value in my case). Everything was working fine when i tested each group in isolation. But as soon as i enable multiple restriction groups (where each group is limited to unique set of accounts), none of my rules work anymore.
What I am trying to configure is to validate our accounts with different sets of rules. We have three subaccount segments, product, customer & area. Some of our accounts require product segment (ie. 000 not allowed), some require product & customer, some require area.
From the training I saw this:
If you are using restriction groups to control the accounts and subaccounts that can be used together,
you must create at least two groups and include all subaccounts in either of the groups. For example,
suppose that you need to restrict visibility of subaccounts for only one account. To solve this task, you
create two restriction groups. In the first group with direct restriction, you include a GL account and the
list of subaccounts that should be related to this account. In the second group with inverse restriction,
you include the same account and subaccounts that should not be displayed after users select this
account. As a result, when users select the account on a form, they will see only one of the subaccounts
included in the first group.
So I setup pairs of groups for each rule structure, where each pair has the same set of accounts, but different subaccount (segment values) so that all values appear in one or the other group. This works fine when only one pair of restriction groups are active, but as soon as i activate both, it doesn't function as expected.
I did not select any users in the groups as the restrictions are global.
Has anyone managed to make sense of account / subaccount row level security and actually managed to get it working?
So no one's done Account / Subaccount restrictions ? Our partner can't help either it seems.
@roycelithgo Did you ever find a solution here? I'm trying to do something similar with account/subaccount restrictions. Would appreciate any help.
I think you can add them manually to the GL Account Access (GL104000) screen.
Trying this for Group Type A since Group Type A Inverse, B, and B Inverse make my head hurt.
Let's say I have a Group Name of Cash Account Access with these GL Accounts included:
Then I have another Group Name of Fixed Asset Account Branch Access.
By default, it looks like GL Account 10100 isn't available to be added to the group:
But I can manually add it by clicking the + button, selecting the GL Account, and checking the box on the line:
When you save, it should remain in the Group Name of Fixed Asset Account Branch Access.
And yet it's still in the Group Name of Cash Account Access:
Online Members