Binding Rules for Oracle Financials Cloud General Ledger Applications

Binding rules ensure that an Oracle Financials Cloud General Ledger application in Oracle Enterprise Data Management Cloud conforms to the requirements of the external application. The following table describes the binding rules for Oracle Financials Cloud General Ledger.

Object	Rule
Node Type	You cannot remove any required binding properties from a bound node type.
Hierarchy Set	You cannot edit the node type in bound hierarchy sets.
Node Set	For bound node sets: You cannot edit the node type in bound node sets. For hierarchy node sets (trees), 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. For list node sets (value sets), the node types are also checked. For hierarchy node sets (trees), the hierarchy set is checked and then the node types are checked.
Dimension/Segment (Value Sets and Trees)	When you edit a viewpoint that is bound to a dimension, you can select a different viewpoint for the binding. The new viewpoint and all of the associated data objects in the data chain are checked for binding rules.

Note:

You can remove a segment (dimension) by deleting it from the application registration. The dimension will continue to be displayed in the application inspector with all of its bound viewpoints to the value set and trees, and you can create data chain objects using the dimension, but it cannot be used for importing or exporting data.

You can remove trees from the segment by deleting them from the application registration. The viewpoints for the trees are not deleted, but they become unbound and cannot be used for importing or exporting data. See Modifying Registered Oracle Financials Cloud General Ledger Applications.