Answer / mahmoud maher

Security rules: Restrict values from responsibility

Cross Validations: Restrict invalid combinations in the
Accounting flexfield
ext. Account with Cost Centers

Answer / arvind

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. 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 single segment.
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.
Cross Validation Rules: Prevents Entering Invalid
Combinations, Security Rules: Restricts the users to
accessing the Responsibilities

Answer / sudhakar

Cross validations rules are Assigned at Chart of Accounts
level.
Security Rules are assigned at Responsibility Level.

When we assign Cross validation rules, list of valuesi.e
account code combinations are visible, but we will get some
error message at the time of usage.

Where as in security rules we are unable to see code
combinations in Lov.

Answer / bhargava athuluri

Security Rule:
To limit the access of different segment values for
different responsibilities. It will work based on
Responsibilities.

Cross validation:
To control the combination values (Account code
combinations). It will work on entire structure.

Answer / maninder singh sandhu

Security Rules:
1. Specific to responsibility
2. Restrict to define segment value
3. Available for both KFF & DFF

Cross Validation Rules:
1. The CVR are specific to COA
2. Restrict the Combination
3. Available for KFF

Answer / prasad

Security Rule :-

Rule set at Segment Level
Works at Responsibility Level
Restrict the user for Invalid Segment accounting
Can't view restricted Values

Cross Validation Rule :-

Rule set at Structure Level
Works at COA Level
Restrict the user for Invalid Code Combination accounting
Can view restricted Code Combination

Thanks,
Prasad

Answer / shrikant

On top of the above answer, CVR is applicable for values
entered from any responsibily. However security rules are
applicable for the responsibilities specified while
defining the rule

Answer / jadugar

Shrikant answer is correct for both Security Rules and
Cross Validation Rules.

Answer / ravi

SECURITY RULE-it works on segments(to enable or disable ) a
particular segment

Cross validation-It used to restrict the particular
accounting code combination , it works on singel accounts
segment.

Difference between quick payment and manual payment?

2 Answers   ICICI,

What are the asset types in FA Module?

5 Answers  

What are the mondatory steps for Receivable module before entering transactions ?

5 Answers   HCL,

What is a Payable Document?

6 Answers   HCL, IBM, Oracle, TCS,

How do you adjust receivables?

0 Answers   IBM,

While Performing Data Migration from Legacy system to Oracle what are the requisites you will perform as a functional consultant for GL, AP, AR, and PO.

1 Answers   Hitachi,

Difference between header level tax calculation and line level tax calculation?

2 Answers  

What is use of AP Accounting Periods?

4 Answers   HCL, IBM, TCS,

How can i increase the number of invoices at the time of payment. Actualty in my setup it will not take more than 300 invoices. plz suggest.

2 Answers  

How should we manage Open balances of accounts while importing legal systems to Oracle at the time of implementation?

0 Answers   Wipro,

Expalin sequence in brief in R12 in general Ledger module. what are major changes around this functionality?

2 Answers  

What is the difference between Quick addition and detail addition?

1 Answers