Best Practices for "Inherit Segment Value Attributes" and "Cross-Validation Rule Violation Report"

Summary

What is the best way to manage the disabling of account combinations in General Ledger?

Content

I am looking to do some cleanup of account combinations that should not be used in our general ledger cloud application.  There are strings containing end dated segment members that we do not want used.  We've found that the "inherit segment value attributes" job will deactivate the strings containing end dated members.  However, some strings without end dated members that were previously deactivated will then be activated.  To partially remedy this, we want to run the cross-validation rule violation report for all CVRs to disable the strings that should be blocked by the CVRs.