Seven Steps for Optimizing Cross-Validation Rules in General Ledger

Share on facebook
Share on twitter
Share on linkedin
Share on email

Cross-validation rules (CVRs) determine which segment values in your chart of accounts (or other
key flexfields) can be used together. Upon data entry, the rule determines and controls the valid
values that may be used in conjunction with other values. Here is a list of the top seven things to remember when designing cross-validation rules in Oracle® E-Business Suite.

  1.  Design your chart of accounts with cross-validation rules in mind.
    Keep values in ranges, put similar data in only one segment, and keep each segment for only one type of data (use alphanumerics only when necessary).
  2.  Start each rule with an Include statement that includes the entire range of values.
  3.  Limit each rule to only two segments.
  4.  Make your error messages very descriptive.
    When a user gets an error, he or she will better understand what changes need to be made to the entered code combination.
  5.  Use several simple rules rather than one complex rule.
  6.  Start your cross-validation Error Messages with CV.
    This lets the user knows when he or she gets an error message that the combination is failing because of a cross-validation rule as opposed to a security rule, or an end-dated value.
  7.  Use a single chart of accounts for all your operations.
    This greatly reduces the number of cross-validation rules necessary.

Leave a Reply

Your email address will not be published. Required fields are marked *