<Enter Concept Title Here>

Folders (segments) and user groups that are designated for the import should be present in the target.
The source and target environment should have the same installed languages. OFSAA supports 18 languages in total. In case of a particular language during export operations, only the specified objects having the same language is exported.
OFSAA users should have access to folders (Infodom segment mapping) in target as well as source. This access is required to get the objects in its state as available in the source, to perform actions such as view and edit.
Tables accessible to users in source should also exist in target. For example, if you want to migrate a Data Element Filter based on "Table A" and "Table B" in the source, those two tables should exist in the target.

Note:
Before you migrate F2T, migrate the respective Data Source files to the Target Environment or create them in the Target Environment.
For AMHM Dimensions and Hierarchies:
- The key processing Dimensions should be the same in both the source and target environments.
- For Member migration, the Dimension type should have the same attributes in both source and target environments.
- Numeric Dimension Member IDs should be the same in both the source and target environments, to ensure the integrity of any Member-based objects.
  Note:
  
  If you have used the Master Table approach for loading Dimension data and set it up to generate surrogate keys for Members, this results in different IDs between the source and target, so it may cause errors if you have objects which depend on these IDs
  
  All objects that generate new ID after migrating to a different information domain and all components which are registered through the Component Registration window, which will be used in the Run Rule Framework (RRF), must be manually entered in AAI_OBJ_REF_UPDATE table in the Configuration Schema. The attributes present in the table are:
  - ```
  V_OBJECT_TYPE- EPM
```
  Object Type
- ```
V_RRF_OBJECT_TYPE- RRF
```
    object Type. The ID can be referred from pr2_component_master table.
- ```
V_ICC_OBJECT_TYPE- ICC
```
  object type, can be referred from component_master table.
- ```
F_IS_FILTER-
```
  Is the object to be migrated as a filter/not?
- ```
N_BATCH_PARAMETER_ORDER
```
  - The order of parameter in task (if used in a batch).