What is the difference between cross-validation rules and security-rules?

  • Interview Candidate
  • 40
  • 27805

Showing Answers 1 - 40 of 40 Answers

sunny

  • Jul 26th, 2005
 

Cross Validation Rules check from users entering invalid combinations of segments whereas 
Security rules checks if changes could be made to certain characteristics after a certain point.

  Was this answer useful?  Yes

Harish

  • Aug 17th, 2005
 

Security rule is applied at a responsibility/User level whereas Cross validation rule is applicable for the given accounting combination. Secondly, Cross Validation rule applicable on the whole combination whereas security rule works on a signle segment.

tgs100

  • Dec 12th, 2005
 

Cross validation rules prevent all the responsibilities/users entering
invalid account combinations. Security rules are attached to specific responsibilities to prevent using few of the segment values for a segment.

  Was this answer useful?  Yes

Prasad Patkar

  • Apr 20th, 2006
 

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.

  Was this answer useful?  Yes

Anjani Kumar

  • May 30th, 2006
 

Cross Validation Rule applies across the chart of account where Security Rule is applicable at Responsibility Level or User Leve.

  Was this answer useful?  Yes

NISHANT KUMAR

  • Aug 5th, 2006
 

CVR is linked with accounting flexifield while security rule is attached to responsibility.

  Was this answer useful?  Yes

Jagan

  • Sep 27th, 2006
 

Cross Validation Rules are meant for defining the set of combinations that are excluded from the global set whereas Security Rules are to restrict Users/Responsibilities from using even the available combinations for security reasons.

  Was this answer useful?  Yes

Bonthu Nagi Reddy

  • Dec 5th, 2006
 

Cross Validation Rules : Prevents Entering Invalid Combinations

Security Rules: Restricts the users to accessing the Responsibilites.

Thanks n Rgds,

Bonthu N Reddy.

  Was this answer useful?  Yes

Muthyala

  • May 10th, 2007
 

Cross-Validation Rules are using for control the certain code combination.


Security Rules are using for control the certain segment values.


Rgds
Muthyala

  Was this answer useful?  Yes

I.visweswara reddy

  • Jun 25th, 2007
 

Cross validation rules will work in the entire application level where as,  security rules are applied to segments.

  Was this answer useful?  Yes

rafee

  • Aug 25th, 2007
 

Both are the security rules only but cross validation rule for range of accounting code combination.
Security rule can be applied for a specific segment.

regards
rafee

  Was this answer useful?  Yes

sm121972

  • Jun 12th, 2008
 

 

Security rules for restricted segment values that user can enter during data entry. The list of values will only display that are not restricted by security rules assigned to the responsibility whenever your user logged on as. Security rules can be applied to KFF and DFF.
Cross-Validations Rules are used to define valid flexfield combination. CRV ruled define whether segment values of particular segment can be combined with other segment values of other segment of same key flexfield. CRV can be applied to KFF only. exceptions Inventory flexfields. CRV is required after enabling dynamic insertation.

sudhamba44

  • May 26th, 2010
 

1. Cross validations rules are assigned at chart of accounts level, where as security rules are assigned at segment level.

2. By assigning cross validation rules at chart of accounts level, the user dont have access to that particular segment. While user try to do any transaction to that segement he will get a pop up message or error message.

3. By assigning security rules at segement level the user do not have access to that segment values e.g. take Account segment.. values i.e expense or revenue or liability or asset.  User will not be able to see that values in LOV.

  Was this answer useful?  Yes

viren56

  • Oct 19th, 2011
 

Thats correct !
1. CVR rules prevent everyone to enter invalid combination of COA segments while
2. Security rules prevent certain users/ responsibilities to use some particular values of COA segments due to security reasons.

  Was this answer useful?  Yes

bhavana.

  • Nov 4th, 2011
 

Cross Validation Restricts the code combination and they values are displayed but not used.

Security Rule restricts the particular segment value and the values are not displayed to use.

  Was this answer useful?  Yes

archanav1409

  • Jan 6th, 2012
 

Cross Validation Rule:- CVR is blocking a particular code combination so that no one can see and use that code combination like:-

Company ABC wants that no one from accounts can enter the snacks expenses so they will block that code combination.
001.002.002794.000.000 This combination is blocked and no one can enter data of this CCID.

Security Rule:- Security rules are based on responsibility level. Like for a particular responsibility u can block a particular segment. User will enter data but he cant see that segment so he cant enter data in that segment.

  Was this answer useful?  Yes

Mahesh

  • Apr 26th, 2012
 

CVR: Restrict the users of particular combination values

Security rule: To use particular values group of values are must implemented

  Was this answer useful?  Yes

Nabeel Ikhlas

  • Aug 9th, 2012
 

CVR; restriction of invalid combination in Char of Account Level

Security Rules; To restrict of Segment values at responsibility level

  Was this answer useful?  Yes

Give your answer:

If you think the above answer is not correct, Please select a reason and add your answer below.

 

Related Answered Questions

 

Related Open Questions