We'd love to hear from you! Provide  feedback  to earn a badge today. Take our quick survey
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

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

Received Response
24
Views
2
Comments
edited Apr 30, 2021 5:38PM in General Ledger & Intercompany 2 comments

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. 

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!