The Tools>Totalto>Orphan Search command lets you search for orphan accounts.
The command helps to determine why a proof account is non-zero, that is, why books appear to be out of balance. Note that books are never really out of balance as debits always equal credits. They only appear to be out of balance, almost always due to omitting to hook an account into the totalto structure; hence the term orphan.
The basic idea behind an orphan search is to select a set of accounts, which we will call the proof accounts, and run the search. The result is a report listing all of the posting accounts in the books that don't total to at least one of the selected proof accounts.
There are several places within the set of books that you can issue the orphan search command and a number of ways that you can select a set of proof accounts:
On any table of accounts (blue):
If no block is marked, the proof account graph will be single account on which you are currently positioned. If you select a set of accounts using block commands, it will be used as the list of proof accounts.
On the proof control view:
Click the NewViews object in a tree explorer and then click on the Proof Control tab to display the proof control view. Each row of the proof control view has a field with a list of proof accounts. Although the proof control view was designed to be used for proof control operations, you can use it for other things as well, such as specifying a set of accounts for use in an orphan search. Add one or more rows, giving them appropriate names and descriptions, and simply do not fill in the Tag List field. Any row with an empty tag list is skipped by any proof check operations, so it can be used for other purposes without interfering with proof check operations.
If you position on a proof control row and issue the orphan search command, the search will use the set of accounts in the Proof Account List field. Or you can select a set of proof control rows and union of the accounts in their Proof Account List fields will be used.
Using these techniques, the proof control view is a good place for specifying sets of proof accounts to be used in an orphan search. Your account selections are also persistent because they are stored in proof control rows.
Note: Only users granted access to the root account (or any object above it) can use this command. Otherwise this would be a breach of the security system since lists of accounts to which the user has not been granted access could be displayed.