Binding Rules for Planning and FreeForm Applications

Binding rules are essential because they automatically make the Oracle Enterprise Data Management Cloud application conform to the requirements of the external application.

The following table describes the binding rules for Planning and FreeForm applications.

Object	Rule
Node Type	You cannot remove any required binding properties from a bound node type.
Hierarchy Set	For bound hierarchy sets, you cannot select a node type that is missing required dimension properties unless you confirm that the system may add the properties when you save.
Node Set	For bound node sets, you must select a hierarchy set that passes its own binding rules and any binding rules up the data chain.
Viewpoint	For bound viewpoints, you must select a node set that passes its own binding rules and any binding rules up the data chain. The hierarchy set is checked and then the node types are checked.
Dimension	When you edit a viewpoint bound to a dimension: You can select a different viewpoint for the binding to a dimension. The new viewpoint is checked for binding rules as are all data objects up the data chain. Note: You can also remove a dimension by deleting it from the application registration. The dimension still displays in the Application Inspector, and data chain objects may be created using the dimension, but it cannot be used for importing or exporting data. In the application import and export sections, you must select a dimension that passes its own binding rules or any binding rules up the data chain.

For more information, see:

• Understanding Binding Rules
• Binding Rules for All Application Types