Security Rule Vs Cross Validation Rules

Cross Validation Rule: Rules that define valid combinations of segment values a user can enter in an account. Cross-validation rules restrict users from entering invalid combinations of account segment values.

Security Rule: It determines the accounting transaction user can view at differenty levels of hierarchy, such as at Site Level -->Application Level --> Responsibility Level --> User level.  

OR-------------------------------------

 

Security rules are segment specific and enforce predefined restrictions of a particular segment. After defining a security rule for the security rule to take affect it should be assigned to a responsibility.

Cross validation rules prohibit invalid account combinations being created thus they are applicable to a combination of segment values. Cross validation rule once created would immediately take affect with all the responsibilities that are using the accounting structure(chart of accounts) for which the rule is defined.

Security rules applies at Value Set level while Cross Validation Rule applies on Segment values.  

OR-----------------------------------

a. Cross Validation rules – Rules that restrict the
user from entering invalid key-flexfield segment value
combinations while data entry. E.g. you may set up a cross
validation rule that disallows using department segments
with balance sheet accounts
b. Security Rules – A rule that allows restriction on
segment values or ranges of segment values for a specific
user responsibility 

 

OR------------------------------------------

Cross Validation Rules(CVS)

• Cross Validation Rule applies on Segment values.
• Cross validation rules prohibit invalid account combinations
• Cross validation rule once created would immediately take affect with all the responsibilities

Security Rule(SR)

• Security rules applies at Value Set level while
• SR restrict user dedine segment values
• security rule to take affect it should be assigned to a responsibility