1. How do I enable cross validation?
1. Using General Ledger Super User Responsibility, navigate to: Setup > Financials > Flexfield > Key > Segments
2. Check checkbox for Cross Validate Segments
3. Save
If this is not done then, when you navigate to Setup > Financials > Flexfield > Key > Rules:
- your Rules will not work
and / or
- you will not see anything in your list of values for Application Structure and Flexfield Title.
2. Check checkbox for Cross Validate Segments
3. Save
If this is not done then, when you navigate to Setup > Financials > Flexfield > Key > Rules:
- your Rules will not work
and / or
- you will not see anything in your list of values for Application Structure and Flexfield Title.
2. Why are my cross validation rules not working?
After turning on the cross validation rules, they are not taking effect and some accounts that should be rejected are still valid.
Possibly the account code combinations were created before your rules were established.
You may have to disable these code combinations, if they are no longer considered valid, via Setup > Account > Combinations or by running the Cross-Validation Rule Violation Report.
This is the way the system works - Rules are not retroactive. They apply only to new code combinations created after the rules are defined and enabled.
Possibly the account code combinations were created before your rules were established.
You may have to disable these code combinations, if they are no longer considered valid, via Setup > Account > Combinations or by running the Cross-Validation Rule Violation Report.
This is the way the system works - Rules are not retroactive. They apply only to new code combinations created after the rules are defined and enabled.
3. Can I use parent values in your cross-validation rules?
The cross-validation rules are independent of the value hierarchy.
If a parent value is Excluded by a cross-validation rule, its children are not excluded unless the child values also fall under the Exclude range.
If a parent value is Excluded by a cross-validation rule, its children are not excluded unless the child values also fall under the Exclude range.
4. How are cross validation rules evaluated?
To pass a rule, a combination must be included in at least one Include element, and must not be included in any Exclude element.
The combination is considered to be included in an element if all of the segment values fall within the low and high range of that include or exclude element.
The Cross Validation Rules are evaluated alphabetically.
The Exclude elements are looked at first.
See Note:1012616.102 for more information.
The combination is considered to be included in an element if all of the segment values fall within the low and high range of that include or exclude element.
The Cross Validation Rules are evaluated alphabetically.
The Exclude elements are looked at first.
See Note:1012616.102 for more information.
5. Where is the Cross-Validation Report and Cross-Validation Rules Listing Report located?
Using system administration responsibility
Navigate to submit > request.
Choose from the list of values.
Navigate to submit > request.
Choose from the list of values.
6. Can the Cross-Validation Rules Violation Report Disable Account Code Combinations?
Yes. The Cross Validation Rule Violation Report allows users to disable existing combinations that violate a cross validation rule. This is the normal functionality of this report.
7. Can I define cross validation rules for a set of books?
No. Cross-Validation rules are defined per accounting flexfield structure.
Any set of books using that structure would operate under the defined cross validation rules for the structure.
Any set of books using that structure would operate under the defined cross validation rules for the structure.
8. Why are code combinations only validated when they are created ?
The main reason is related to the performance for Journal Import, Posting and many other GL or sub-ledger programs - it just would not be acceptable in most of the cases to validate all the cross-validation rules for all the account code combinations involved.
So this is the current option: the validation is only performed at creation time, and this is not expected to change.
If an account becomes invalid due to a validation rule defined by the users, it should just be disabled (using the Cross-Validation Rule Violation Report) and the sub-ledgers that are using it should be setup accordingly so that they do not try to create transactions on incorrect accounts.
GL expects that only enabled and valid accounts are used by the sub-ledgers. This is referred to in the General Ledger User's Guide: Journal Entry: Importing Journals: About Journal Import Validation: Account Validation:
"Account Validation
Journal Import validates your account code combinations in a number of ways. JournalImport will successfully import your accounting data if your code combinations meetthe following validation requirements:
You allow detail posting to segment combinations.
You have enabled your code combinations for the accounting date you specify.
Your code combinations do not include summary accounts."
So this is the current option: the validation is only performed at creation time, and this is not expected to change.
If an account becomes invalid due to a validation rule defined by the users, it should just be disabled (using the Cross-Validation Rule Violation Report) and the sub-ledgers that are using it should be setup accordingly so that they do not try to create transactions on incorrect accounts.
GL expects that only enabled and valid accounts are used by the sub-ledgers. This is referred to in the General Ledger User's Guide: Journal Entry: Importing Journals: About Journal Import Validation: Account Validation:
"Account Validation
Journal Import validates your account code combinations in a number of ways. JournalImport will successfully import your accounting data if your code combinations meetthe following validation requirements:
You allow detail posting to segment combinations.
You have enabled your code combinations for the accounting date you specify.
Your code combinations do not include summary accounts."
9. How do cross validation rules work with MOAC in release 12?
Multiple Operating Units can be accessed through a single responsibility by defining a security profile and assigning it to the responsibility via the 'MO: Security Profile' profile option.
However within the same responsibility Balancing Segment Values (BSVs) cannot be restricted based on the Operating Unit (OU) because security rules are assigned to and work at Responsibility level, not at Operating Unit level.
However within the same responsibility Balancing Segment Values (BSVs) cannot be restricted based on the Operating Unit (OU) because security rules are assigned to and work at Responsibility level, not at Operating Unit level.
10. How can I check if a code combination violates cross validation rules ?
Run the Cross Validation Violation Report from System Administrator Responsibility, or use the sql in note:134006.1.
11. What is MRC and what is its use?
The Multi Reporting Currency Feature allows you to report and maintain records at the transaction level in more than one functional currency. You can do by defining one or more set of books in addition to primary set of books.
The Multi Reporting Currency Feature allows you to report and maintain records at the transaction level in more than one functional currency. You can do by defining one or more set of books in addition to primary set of books.
No comments:
Post a Comment