How to Identify and Correct GL Code Combinations generated before Invoking Security Rules?
Hi,
In our current landscape of R12 Implementation, we have observed on random checks that few GL Code Combinations were generated in Oracle before Security Rules were Setup and Invoked. Consequently, these Invalid (from Security Veiwpoint) Combinations need to be identified and corrected at the earliest (these could be used earlier during a Setup or in Master Data)
Is there a White Paper or Guideline on how to identify all such Combinations (similar to standard Cross Validation Rules Violation Report) and best practice to rectify these?
Thanks,
Abhishek