My Oracle Support Banner

After Implemeting GL Security Rule the "Account generation failed" With "Value secured NNN Can Only Use Value XX" Error Occurs Incorrectly When Using Value That Should Be Allowed By the GL Security Rule (Doc ID 2939280.1)

Last updated on APRIL 05, 2023

Applies to:

Oracle iProcurement - Version 12.2.4 and later
Information in this document applies to any platform.

Symptoms

When attempting to create requisitions after enabling a Security Rule on a GL Account Segment the following error occurs when the Charge Account includes a Value that the Security Rule should allow to be used.  

In the below error message NNNN is the name of the Account Segment and XXXX is the value(s) that are allowed




STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. From General Ledger responsibility create Security Rule (see <Note 1078004.6> for details how to create a Security Rule) created for a charge account segment and it includes certain values but also excludes values also that means they are not permitted.
2. From iProcurement responsibility create a requisition where the segment has incorrect values and the error correctly occurs because its not allowed.
3. Click Edit link from this page and enter correct charge account segment values that are permitted by the Security Rule.  Error continues to occur which is incorrect. 

 

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.