what diff b/w security rulues and cross validation rulues
Answers were Sorted based on User's Feedback
Security rules: Restrict values from responsibility
Cross Validations: Restrict invalid combinations in the
Accounting flexfield
ext. Account with Cost Centers
| Is This Answer Correct ? | 6 Yes | 0 No |
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
| Is This Answer Correct ? | 3 Yes | 0 No |
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.
| Is This Answer Correct ? | 1 Yes | 0 No |
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.
| Is This Answer Correct ? | 0 Yes | 0 No |
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
| Is This Answer Correct ? | 0 Yes | 0 No |
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
| Is This Answer Correct ? | 0 Yes | 0 No |
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
| Is This Answer Correct ? | 1 Yes | 2 No |
Answer / jadugar
Shrikant answer is correct for both Security Rules and
Cross Validation Rules.
| Is This Answer Correct ? | 0 Yes | 2 No |
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.
| Is This Answer Correct ? | 0 Yes | 6 No |
What are the components of Set of Books?
How can the new account combinations be defined when dynamic insert option is not enabled?
in payable module journal entries
Oracle financials talk of Set of Books. However at the beginning of an implementation, when you talk of set of books to the CFO, he will most likely tell you that 'He has just an accounting book for the organization'. So he feels that he does not need 'Set of Books'. How can you reconcile the above two statements?
What is the difference between Oranisation ID and Org. ID. Is both are same?
How to transfer the funds between internal banks
what are the setup from scrap in R12.?
can we stop the payment once the payment manager process has been run?
what is the difference between bonus reserve and bonus expense
How to open the new future periods in GL while we are in P2P or in O2C
how we can stop the transaction for not transfer to the reporting ledger at the time of entering the transaction in pl
What is write off Accruals? what is the use of this?