Skip to main content
Solved

IFS_GENERAL_LEDGER RLS Missing Combinations

  • May 29, 2026
  • 2 replies
  • 17 views
J
Do Gooder (Customer)
Forum|alt.badge.img+3
  • jdual
  • Do Gooder (Customer)

Hi Everyone

On the Page “AD User Mappings for Financial Models” one can Generate Access for General Ledger Code Combinations. In some Cases not all Combinations get generated namely.

GL Authority Combinations (We only use it on Account and Cost Center, all other Elements are %)
MAX: Account = %, Cost Center = %

Voucher Row:
Account = 24790, Cost Center = null
This Combination is Missing in the [CODESTRING_COMBINATION_RLS_BI_TAB] and therefore RLS is not working properly in GL Analysis Model.

The Generate Access Procedure must include null combinations. Currently it only takes combinations into account where the code part exists in code part values, but a combination of account without any other posting element ist very viable.

 

Best answer by jdual

Hi ​@subashfestus 

I think we cannot directly create support cases. In our Test environment we are on 25.1.11, in 25.1 RLS got updated.

“RLS implementation of Code Part Combinations was updated.”

I can point you towards the right direction.
1. ROW_LEVEL_SECURITY_UTIL_API.GENERATE_TABM_USER_COMB_ACCESS
In this procedure the following procedure gets called
2. ROW_LEVEL_SECURITY_UTIL_API.Get_Codestring_Combinations___
=> This is where the issue lies.
“cmb.code_b  IN (SELECT code_part_value FROM accounting_code_part_value_tab val  WHERE code_part = ''B'' AND company = glu.company)”
With this snipped code_b Values have to be in the code_par_values, this means all null values get removed and therefore combinations Account = 24790, code_b  = null are not included.

Hotfix
“(cmb.code_b  is null or cmb.code_b  IN (SELECT code_part_value FROM accounting_code_part_value_tab val  WHERE code_part = ''B'' AND company = glu.company))”

Since Code_b can be null it has to be included, one could even remove the whole IN Statement, since 

Best regards,
Joel

2 replies

S
Hero (Employee)
Forum|alt.badge.img+7
  • subashfestus
  • Hero (Employee)
  • June 5, 2026

Hi ​@jdual,

What is the application version you are using?
Can you create a support ticket for this with more information about the setup you have in auth combinations.

Then we (RnD) can try to investigate and recreate the issue to understand where the issue is.

Thank you.

Best regards,

Subash 

J
Do Gooder (Customer)
Forum|alt.badge.img+3
  • jdual
  • Author
  • Do Gooder (Customer)
  • Answer
  • June 5, 2026

Hi ​@subashfestus 

I think we cannot directly create support cases. In our Test environment we are on 25.1.11, in 25.1 RLS got updated.

“RLS implementation of Code Part Combinations was updated.”

I can point you towards the right direction.
1. ROW_LEVEL_SECURITY_UTIL_API.GENERATE_TABM_USER_COMB_ACCESS
In this procedure the following procedure gets called
2. ROW_LEVEL_SECURITY_UTIL_API.Get_Codestring_Combinations___
=> This is where the issue lies.
“cmb.code_b  IN (SELECT code_part_value FROM accounting_code_part_value_tab val  WHERE code_part = ''B'' AND company = glu.company)”
With this snipped code_b Values have to be in the code_par_values, this means all null values get removed and therefore combinations Account = 24790, code_b  = null are not included.

Hotfix
“(cmb.code_b  is null or cmb.code_b  IN (SELECT code_part_value FROM accounting_code_part_value_tab val  WHERE code_part = ''B'' AND company = glu.company))”

Since Code_b can be null it has to be included, one could even remove the whole IN Statement, since 

Best regards,
Joel

Terms & ConditionsAccessibility statement