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.

Explain Secondary Tracking Segments.

1 Answers  

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,

In Oracle GL how to review the accounts associated with the financial statements?

1 Answers  

how to create a journal source by user9

1 Answers   Logica CMG,

Which factor decide how many segment in our structure?

1 Answers   Deloitte,

what is the use of matching tab in payables options in Payables module?

1 Answers   Genesis,

Can two users use same payable document simultaneously? If yes, which user will get the document number assigned first?

2 Answers  

What is Intercompany Invoicing?

5 Answers  

What are the mandatory flexfiels used in FA?

3 Answers  

What is the difference between Electronic fund transfer and wire?

1 Answers   Genesis,

Why Retained Earning Account is necessary for the set of book creation while implementing oracle new business.

4 Answers  

What is the Process of Reconciliation Between AP to GL

0 Answers   Wipro,