Managing Export Options

Export options enable you to define keywords to export instead of null or empty values, as well as how validations are run before exporting.

To manage the export options for a dimension, inspect the dimension that you want to export from (see Inspecting Dimensions) and then select the Import/Export tab.

Exporting Keywords Instead of Null and Empty Values

You can export keywords instead of null and empty values for properties. When you export a property that has a null or an empty value, the keyword that you specified in Export Keyword for Null Values or Export Keyword for Empty Strings (for example, <none>) is exported for that property instead of an actual blank value.

Note:

For Planning, Planning Modules, and Financial Consolidation and Close applications, the default keyword for null and empty values is <none>. You can change this keyword, but the target application may not recognize the keyword as a null or empty value. The keyword that you specify is applied only to the properties that support it in the target application:

• Aliases
• Attributes
• Description (unless it is a shared node)
• Formula (always exports the keyword if Data Storage is Shared)
• Formula Description (always exports the keyword if Data Storage is Shared. If it is not shared then it will export a blank value if defined or the keyword if default is blank )
• Smart List (unless it is a shared node)
• UDA

Additionally, the null or empty value keyword is not exported for any predefined members.

Tip:

If the application that you are exporting to does not differentiate between null and empty values, you should use the same keyword for both Export Keyword for Null Values and Export Keyword for Empty Strings.

Validating Viewpoints before Exporting Dimensions

To ensure data integrity, you can use the Validate Before Export option to specify whether or not the viewpoint for a dimension gets automatically validated when you export the dimension or mapping. Choose from these options:

• Disabled (Default): Validations are not run before export.
• Alert on Error: Validations for the bound viewpoints for the dimension with a severity of Error (see Understanding Validation Severity) are run before the export is performed. If there are validation failures, the user is alerted but the export will still be performed. Validation failures and export results are displayed in the History section of the export screen.
• Discontinue on Error: Validations for the bound viewpoints for the dimension with a severity of Error (see Understanding Validation Severity) are run before the export is performed. If there are validation failures, the user is alerted and the export is discontinued. Validation failures and export results are displayed in the History section of the export screen.

Note:

All system, application-level, and custom validations as well as all constraints are run when Validate Before Export is performed. See Understanding Validations and Constraints.

If there are export validation issues, click the Viewpoint(s) link to open the viewpoint and resolve the issues. See Resolving Validation Issues.

When you have finished resolving the validation issues, from the viewpoint pane click Back to Export to return to the export screen.

Oracle Financials Cloud General Ledger Export Options

For Oracle Financials Cloud General Ledger dimension exports to a connection only, you can configure export options to include additional post-export tasks that initiate the import and publishing processes in the external Financials Cloud environment and complete the synchronization of segment values and trees. After you enable the export options, they are executed each time you export the dimension to an Oracle Financials Cloud General Ledger connection.

The following options are available:

• Import Segment Values and Hierarchies: Updates the Financials Cloud segment values and hierarchies in the external application with the values being exported.

  Note:

  The user running the export must have the GL_LOAD_ACCOUNT_VALUES_AND_HIERARCHIES_PRIV privilege in Oracle ERP Cloud.
• Process Segment Values and Hierarchies: Submits processes in the external system related to account hierarchies, such as row and column flattening, tree audit and activation, maintain value sets and account hierarchies processes, and publish hierarchies process.

  Note:

  The user running the export must have the following privileges in Oracle ERP Cloud:

  • GL_LOAD_ACCOUNT_VALUES_AND_HIERARCHIES_PRIV
  • FND_APP_MANAGE_FLEXFIELD_VALUE_SET_PRIV
• Publish Hierarchies to Cube: Creates and updates chart of accounts dimension members and hierarchies for the balances cubes.

  Note:

  The user running the export must have the following privileges in Oracle ERP Cloud:

  • GL_LOAD_ACCOUNT_VALUES_AND_HIERARCHIES_PRIV
  • FND_APP_MANAGE_FLEXFIELD_VALUE_SET_PRIV

Note:

For the Process Segment Values and Hierarchies and Publish Hierarchies to Cube options, the integration tasks are executed in Oracle Financials Cloud General Ledger only on the trees and tree versions that were exported from Oracle Enterprise Data Management Cloud.

By default, all export options are deselected, and only the first option can be selected. When you select each option, the next option becomes available to be selected. For example, you must select Import Segment Values and Hierarchies before you can select Process Segment Values and Hierarchies.

If you deselect an option, all selected options below that option are cleared.