Wednesday, 28 November 2018

Cross validation rules and security rules in oracle apps

Cross validation rules and security rules in oracle apps

Here we will discuss about cross validation rules and security rules in oracle apps. These are two Security rules available in the Oracle application for Char of Accounts (KFF). We can put restrictions and security on Accounting KFF or chart of Accounts using these rules. Both rules have different way of Functioning and different set of features too. The common seminaries between cross validation rules and security rule is only that for works for KFF or Chart of accounts. Here in this Post, I will be explain in detail about cross validation rules and security rules in oracle apps.
 

Detail Explanation of cross validation rules and security rules in oracle apps

 
1.Security rules : -
 
This is the simple Security Concept in the KFF, We can Exclude some of the values of Chart of Accounts Segments to be used by business Users. The good part of this Rules is that , This rule does not apply to the whole KFF, We can restrict this rule to Specific segment of the KFF and also we can put this Security to the Specific responsibilities not to the Entire Responsibilities like Cross Validation Rule. This rule only work for responsibilities so we have control we can design the different -2 Security rules for different responsibilities based on our Requirment.

How to Define Security Rule in Oracle apps
 
Cross Validation Rules :-
 
The purpose of this rule is more about security and control in the application. We put some restrictions in the  Char of Accounts or in the Accounting Key flex fields using this Cross Validation rules. Cross validation rules we creates in the General Ledger responsibility. These rules works for all Business units based on the Which Chart of Accounts we have applied this cross Validation rule.

1.These Rules only apply to the Char of Account or Key Flex Field Structure.

2.These Rules works Globally , We have no control to restrict these rolls on the basis of User , Responsibility and Business Units.

3.We uses the Cross validation rules to restrict the Key Flex fields segment values so that no user can use these values in the Account KFF during entering the Transactions.
 
 
 

1 comments:

Rifath said...

Brilliant blog I visit this blog it's incredibly awesome. Curiously, in this blog content formed doubtlessly and sensible. The substance of information is helpful.
Oracle Fusion HCM Online Training

Post a Comment

Contact us for any Collaboration, Project Support & On Job Support Work

Name

Email *

Message *