Guidelines for Moving Related Common Reference Objects

Certain common reference objects may use other common reference objects creating dependencies among the objects. During the movement of common reference objects, ensure that these dependencies or references aren't broken or lost.

Dependencies

The dependencies among the common reference objects may be caused by any of the following conditions.

• Flexfield segments use value sets

• Value sets may make use of standard, common, or set-enabled lookups

• Key flexfields may have an associated tree structure and key flexfield segments may have an associated tree code

• Tree codes and versions may be defined over values of a value set

• Data security policies may be defined for value sets that have been enabled for data security

You may decide to move one, some, or all of the business objects by including the ones you want to move in your configuration package. For example, you may decide to move only value sets, or move both value sets and their lookups as part of the same package. Whatever be the combination, Oracle recommends that during the movement of objects, you follow an order that maintains the dependencies among the objects.

While moving the business objects, adhere to the following order:

1. Move created taxonomy modules before moving any objects that reference them, such as flexfields, lookups, profiles, messages, and so on.

2. Move created currencies before moving any objects that reference them, such as territories.

3. Move created territories before moving any objects that reference them, such as languages and natural languages.

4. Move created ISO languages before moving any objects that reference them, such as languages, natural languages, and industries.

5. Move created tree structures before moving any objects that reference them, such as trees or tree labels.

6. Move created profile options before moving any objects that reference them, such as profile categories or profile values.

7. Move created attachment entities before moving any objects that reference them, such as attachment categories that reference them.

Note:

In scenarios where there may be dependencies on other objects, you must move the dependencies before moving the referencing object. For example, if data security policies have dependencies on newly created security roles, you must move the security roles before moving the security policies.