Assumptions Change Manager maintains account information. You select one base entity as the source for all account information, and you select multiple target entities that receive copies of that account information. This is particularly useful to help you ensure uniformity between financial models.
Create Assumptions Change Manager (ACM) documents to define a base entity, or the source of the changes, and the target entities, which receive the changes—and to define the account attribute changes copied from the source to the targets. ACM documents store this information for future use. Unlike Entity Change Manager, you run Assumptions Change Manager only one time per change.