We have several accounting units that are mapped to various GL Account codes per GL20.2. We have one accounting unit for balance sheet transactions, but we discovered several income statement accounts with exists as "yes" on the GL20.2 for the balance sheet unit. We don't want individuals accidently coding transactions improperly so we need to turn the exists from "yes" to "no." We have shut off dynamic account generation to prevent the exists from being turned automatically to "yes" if someone keys the wrong GL account code.
I also built an upload file to do one mass change for all the bad combinations (we have about 2000). The problem is when I upload, if the bad combination has any ANY activity, even though the balance is now "0," I get the following message. "cannot delete; account has actual activity." Is there any way to turn the exists from "yes" to "no" since we made the adjustment so the combination balance in the ledger is now "0," or are we stuck with these active bad combinations in our ledger that we will have to manually monitor?
Thanks!
I also built an upload file to do one mass change for all the bad combinations (we have about 2000). The problem is when I upload, if the bad combination has any ANY activity, even though the balance is now "0," I get the following message. "cannot delete; account has actual activity." Is there any way to turn the exists from "yes" to "no" since we made the adjustment so the combination balance in the ledger is now "0," or are we stuck with these active bad combinations in our ledger that we will have to manually monitor?
Thanks!