Previous  Next          Contents  Index  Navigation  Glossary  Library

Submitting a Move/Merge Request

Caution: We recommend that you purge tables only after you have verified that the moved balances are correct. Once you purge the tables, you cannot reverse the move/merge operation.

Conflicts with Other Processes and Activities

You should only run move/merge operations when no conflicting activity is taking place in the same set of books. There are two categories of activities that conflict with move/merge:

Journal Creation: includes entering manual or budgetary control journals, importing journals, revaluation, MassAllocations, and recurring formulas.

Balance Processing: includes posting, translation, summarization, open period, and purge.

Account Creation: includes creating, modifying, disabling, and enabling accounts.

All concurrent processes and online activity that fall into the above categories should be completed before you initiate a move/merge operation. To minimize the chance of conflicts occurring, we recommend that you establish and enforce procedures for scheduling move/merge operations. We also recommend that you establish and enforce procedures over account creation and modification.

Suggestion: Consider excluding the move/merge concurrent program from the standard concurrent manager. Instead, assign the program to a special concurrent manager queue that becomes active only at specified times.

See Also

Defining a Move/Merge Request

Mass Maintenance Statuses

Validation and Prevalidation

Reversing a Move/Merge

Purging Move/Merge Tables

Creating New Accounts with Mass Creation


         Previous  Next          Contents  Index  Navigation  Glossary  Library