Set Up Security Rules For An Accounting Flexfield Segment

You might also like

Download as txt, pdf, or txt
Download as txt, pdf, or txt
You are on page 1of 4

How Do You Set Up Security Rules For An Accounting Flexfield Segment? [ID 107800 4.

6] -------------------------------------------------------------------------------Modified 19-DEC-2010 Type PROBLEM Status PUBLISHED

Checked for relevance on 20-Aug-2008 Problem Description ------------------You would like to be able to set up value security on a segment of your accounting flexfield and need to know what the process is. You would also like to know how setting up security will affect reporting, for both standard reports and FSGs. Solution Description -------------------There are several steps involved in setting up value security. You need to: I. II. III. IV. V. VI. Enable security on the value set Enable security on the flexfield segment Define the security rules Assign the security rules Freeze and recompile the accounting flexfield Set the FSG:Enforce Segment Value Security profile option

Do this as follows: Responsibility = General Ledger Super User I. Enable security on the value set -------------------------------------1. Navigate to the Value Sets form (FNDFFMVS, Navigation = Setup..Financials..Flexfields..Validation..Sets). 2. Query the Value Set. 3. For 11.0 applications, check the Security Available check box. Save. For 11.5.X applications that have AOL FND.D applied and For 12.0.X ,12.1.X applications, Select Non-Hierarchical Security in the Security Types drop box. Save. II. Enable security on the flexfield segment ---------------------------------------------1. Navigate to the Segment Values form (FNDFFMIS, Navigation = Setup..Financials..Flexfields..Key..Segments). 2. Query your Accounting Flexfield structure. With the cursor in the row containing your accounting flexfield, uncheck the Freeze Flexfield box and Save. 3. With the cursor in the row containing your accounting flexfield,

click the [Segments] button. 4. With the cursor in the row containing the segment you wish to enable security for, click the [Open] button. 5. Click the Security Enabled checkbox. Save. III. Define the security rules ------------------------------1. Navigate to the Define Security Rules form (FNDFFSRN, Navigation = Setup..Financials..Flexfields..Validation..Security..Define). 2. Query your Value Set. 3. Define the Security Rule(s) and Save. Here is an example of how a security rule should be set up. To define a security rule, use the navigation path Setup : Financial : Flexfields : Key : Security : Define. A 'Find' window appears. This is the same Find window as the one used in entering allowable segment values. You can find values by value set, Key flexfield, Descriptive flexfield, or concurrent program. Define security rules by entering a unique name, an optional description, and a mandatory message. This is the message that will appear if the security rule is violated. After you define the security rule, delineate the security rule elements. Similar to cross-validation rule elements, there are two types of security rule elements: Include and Exclude. It is suggested that you define an all-encompassing Include and then several Excludes. The range for security rules is not the entire combination, but only for a specific segment. Enter the security rule elements. Include all possible values and then exclude any values that are to be secured. (Example: before Department 110 and after 130.) Enter the following: Type Include Exclude Exclude From 000 000 131 To ZZZ 109 ZZZ

Please note that if you use multiple includes that overlap, it will be misintepr eted in some cases like ADI, and could cause issues. IV. Assign the security rules ----------------------------1. Navigate to the Assign Security Rules form (FNDFFSRA, Navigation = Setup..Financials..Flexfields..Validation..Security..Assign).

2. Query your Value Set. 3. Assign the Security Rules(s) to a responsibility and Save. V. Freeze and recompile the accounting flexfield --------------------------------------------------1. Navigate to the Segment Values form (FNDFFMIS, Navigation = Setup..Financials..Flexfields..Key..Segments). 2. Query your Accounting Flexfield structure. 3. With the cursor in the row containing your accounting flexfield, check the Freeze Flexfield Definition checkbox. VI. Set the FSG:Enforce Segment Value Security profile option --------------------------------------------------------------1. Sign on a System Administrator responsibility. 2. Navigate to the System Profiles form. 3. Set the profile option FSG:Enforce Segment Value Security to YES at the desired level. Save. FSG Reports, Release 10.7, 11.0.X ,11.5.X, 12.0.X,12.1.X: --------------------------------------------FSG security will prevent another responsibility from viewing segments which they don't have access to. The popup box won't show the secured segment value as a choice. The FSG reports will not include data the responsibility does not have access to. Standard Reports, Release 11.5.X,12.0.X,12.1.X: --------------------------------For Standard reports, a user without the proper responsibility cannot see the segment in the popup box; however, the user can manually type in the segment and then the report will run the segment data. Segment security was implemented in standard reports in Release 11.5.X. There is no security for standard reports in applications releases prior to 11.5.X. Hierarchical Security --------------------As of the AOL FND.D patchset, there is now have another option for setting up security on segments. Please see note #164769.1 and review the section on "Key Flexfield Rollup Hierarchy in Security Rules". This gives the ability to check flex value security based on flex value hierarchy where a flex value should be secured if one of its' parents in a flex value hierarchy is secured. Multiple rules to the same responsibility --------------------------------------------If you have multiple separate rules whose included values do not overlap, then n o values will be allowed at all, because values must be included by all active s ecurity rules for that segment to be valid. In summary, for multiple rules, it is the intersection and not the union of the rules that provides the allowable values for the rule. The recommended is to create a new rule that includes all desired values and the

n assign that to a new responsibility. In case of multiple rules, only those values will appear, that are included in a ll of the rules, and not excluded in any of the rules. References ---------Oracle Applications Flexfields Guide Release 11i, Part #A75393-01 Oracle General Ledger User Guide Release 11i, Part #A82850-01 Additional Search Words ----------------------Define Security Rules, FNDFFSRN Assign Security Rules, FNDFFSRA RGRARG Financial Statement Generator GL Related

-------------------------------------------------------------------------------Products -------------------------------------------------------------------------------Oracle E-Business Suite > Financial Management > Financial Control and Reporting > Oracle General Ledger Oracle E-Business Suite > Financial Management > Financial Control and Reporting > Oracle General Ledger Oracle E-Business Suite > Financial Management > Financial Control and Reporting > Oracle General Ledger Keywords -------------------------------------------------------------------------------FNDFFMIS.FMB; FNDFFMVS.FMB; FNDFFSRN.FMB; SEGMENT VALUES; SECURITY RULE; ASSIGN SECURITY RULES; FLEXFIELD SEGMENTS; FLEXFIELDS

You might also like