Dimension Binding Examples
Binding Examples
Let's look at a binding for a Planning application to understand some binding principles:
Note the following about bindings in this diagram:
- In Planning applications, dimensions can be bound only to a single viewpoint. In this example, the Account dimension is bound to the Account viewpoint, while the Alternate Structures viewpoint is unbound. Since data is imported and exported only to bound viewpoints, import and export operations will not affect the Alternate Structures viewpoint. See Importing Dimensions.
- The Account binding is between the Account dimension and the Account viewpoint in Oracle Enterprise Data Management Cloud. The binding controls the import and export to the Account dimension in the external application, as well as enforcing binding rules within Oracle Enterprise Data Management Cloud.
- All of the data chain objects contained within the Account viewpoint are also bound to the Account dimension.
Now let's look at a binding for an Oracle Financials Cloud General Ledger application:
Oracle Financials Cloud General Ledger applications support binding a dimension to multiple viewpoints. In this example, the Account dimension in Oracle Enterprise Data Management Cloud is bound to three viewpoints. Each binding controls the import and export to a specific data structure in the external application and enforces binding rules within Oracle Enterprise Data Management Cloud:
- Account Viewpoint binding— controls the import and export to the Account value set in the external application.
- Corporate Account V1 viewpoint binding— controls the import and export to the Corporate Account V1 tree version in the external application.
- Corporate Account V2 viewpoint binding— controls the import and export to the Corporate Account V2 tree version in the external application.
See Working with Oracle Financials Cloud General Ledger Applications for more information about the Oracle Financials Cloud General Ledger information model.