Understanding Binding Rules

Binding rules ensure that users cannot make changes that would prevent an application's data from being imported or exported. In other words, binding rules ensure that a registered application conforms to the external application's requirements. Binding rules vary by application type. For example, Oracle Financials Cloud General Ledger applications support multiple bindings per dimension, while Planning applications support a single binding per dimension.

Binding rules are enforced on the viewpoint and related data objects that are bound to a dimension. When you register an application, Oracle Enterprise Data Management Cloud creates the bound viewpoint and related data chain objects. The bound data objects store and display the data that is managed, imported, and exported, see Understanding Bindings and Bound Data Objects.

Tip:

If you change the bound viewpoint, the dimension will be bound to the data objects on the viewpoint's data chain.

Binding rules are enforced when users perform the following tasks:

Updating a bound data object. If a change would violate a binding rule, then Oracle Enterprise Data Management Cloud prevents the change from being made.
Updating the viewpoint bound to a dimension.

For example, suppose a dimension does not allow shared nodes. A binding rule prevents users from enabling shared nodes in the hierarchy set bound to the dimension.

Note:

Only data objects bound to a dimension must conform with the binding rules. Unbound data objects enable you to model and evaluate potential changes to dimensions in cases where the changes would not conform with a dimension's current binding rules.

There are basic binding rules that apply to all application types. Some application types have additional binding rules.

For more information, see: