Oracle Fusion Functional Setup Manager User's Guide

Skip Headers

Home

Contents

Book
List

Contact
Us

PDF

Configuration Packages: Explained

Exporting and Importing Setup Data: Explained

Customizing Configuration Packages: Points to Consider

Business Objects Marked as Scope Parameters: How They are Exported

Business Object Import Sequence: Explained

Export Scope: Explained

FAQs for Importing and Exporting Setup Data

Configuration Packages: Explained

Almost all Oracle Fusion application implementations require moving functional setup data from one instance into another at various points in the lifecycle of the applications. For example, one of the typical cases in any enterprise application implementation is to first implement in a development or test application instance and then deploy to a production application instance after thorough testing. You can move functional setup configurations of applications from one application instance into another by exporting and importing Configuration packages from the Manage Configuration Packages page.

A Configuration Package contains the setup import and export definition. The setup import and export definition is the list of setup tasks and their associated business objects that identifies the setup data for export as well as the data itself. When you create a configuration package only the setup export and import definition exists. Once you export the configuration package appropriate setup data is added to the configuration package using the definition. Once a configuration package is exported, the setup export and import definition is locked and cannot be changed.

You generate the setup export and import definition by selecting an implementation project and creating a configuration package. The tasks and their associated business objects in the selected implementation project define the setup export and import definition for the configuration package. In addition, the sequence of the tasks in the implementation project determine the export and import sequence.

Exporting and Importing Setup Data: Explained

A configuration package is required to export setup data. You can export a configuration package once you create it, or at any time in the future. During export, appropriate setup data will be identified based on the setup export definition and added to the configuration package. The setup data in the configuration package is a snapshot of the data in the source application instance at the time of export. After the export completes, you can download the configuration package as a zipped archive of multiple XML files, move it to the target application instance, and upload and import it.

Export

You can export a configuration package multiple times by creating multiple versions. While the export definition remains the same in each version, the setup data can be different if you modified the data in the time period between the different runs of the export process. Since each version of the configuration package has a snapshot of the data in the source instance, you can compare and analyze various versions of the configuration package to see how the setup data changed.

Import

In the target application instance, the setup import process will insert all new data from the source configuration package that does not already exist and update any existing data with changes from the source. Setup data that exists in the target instance but not in source will remain unchanged.

Export and Import Reports

You can review the results of the export and import processes using reports. The results appear ordered by business objects and include information on any errors encountered during the export or import process. If a setup export or import process paused due to errors encountered or for a manual task to be performed outside of the application, then you can resume the paused process.

These reports show what setup data was exported or imported and by which specific process. You can change the reports to validate the setup data as well as to compare or analyze it. A report is generated for each business object. These reports show the same information as the export and import results seen directly in the application.

Process status details are available as text files showing the status of an export or import process including the errors encountered during the process.

Customizing Configuration Packages: Points to Consider

All tasks and associated business objects in the selected implementation project are included in the setup export and import definition of a configuration package. You can customize the setup export and import definition.

Excluding Business Objects

If you do not want to export any specific setup data, you can exclude the corresponding business object from the setup data export and import definition of the configuration package.

Reordering Business Objects

You can change the sequence in which setup data is exported and consequently imported by changing the sequence of the business objects in the setup export and import definition of your configuration package. The default export and import order of setup data, or business objects, is the same as the order of the tasks they are associated with in the implementation project.

Filtering Setup Data

All setup data from all business objects in the setup export and import definition is exported by default. However, you can filter exported setup data by specific export scope values if the business object has a scope selection for setup data export. During export, you might have the option to choose specific scope values. For any setup data where scope is applicable, only the data that matches the selected values will transfer.

Business Objects Marked as Scope Parameters: How They are Exported

When creating a configuration package, you may see some business objects that are used as scope parameters for data filtering. These business objects correspond to parameters used by some tasks within the implementation project as source for the configuration package to filter data.

Settings That Affect Business Object Data Export

The data for business objects used as scope parameters data is not exported because these business objects are not directly associated to any tasks in the implementation project used to create the configuration package.

How Business Object Data Is Exported

Data of dependent business objects is filtered by the selected scope values and exported.

Example

Subledger may have been defined as the scope parameter for receivable data but is not associated with any tasks in the implementation project you selected to create a configuration package. You will find the sub ledger business object listed. While subledger data will not be exported by way of the configuration package, you will have the option to filter receivables data by certain subledgers during export.

Business Object Import Sequence: Explained

The setup data for business objects related to tasks are imported according to the import sequence. The default business object import sequence is derived based on the sequence of the tasks within the implementation project selected to create the configuration package. This is because the task sequence in the implementation projects should be congruent to the sequence you need to enter the related data to prevent dependency failures. You can change the default import sequence when creating your configuration package if you are fully aware that such changes will not result in data dependency failures during import.

The application assigns the lowest import sequence number to the business objects associated to the first task and increases the sequence number for the successive tasks.

The following business objects are exceptions to the rule and they are always exported and imported before any other business objects in this sequence:

Business Object Name	Business Object ID
Application Taxonomy	FND_APP_TAXONOMY
Application Reference Data Set	FND_APP_REFERENCE_DATA_SET
Application Reference Data Set Assignment	FND_APP_REFERENCE_DATA_SET_ASSIGNMENT
Application Lookup	FND_APP_SET_ENABLED_LOOKUP
Data Security Policy	FND_APP_DATA_SECURITY_POLICY
Application Tree Structure	FND_APP_TREE_STRUCTURE
Application Tree Label	FND_APP_TREE_LABEL
Application Tree	FND_APP_TREE
Application Flex Value Set	FND_APP_FLEX_VALUE_SET
Application Descriptive Flexfield	FND_APP_EXTENSIBLE_FLEXFIELD
Application Extensible Flexfield	FND_APP__FLEXFIELD
Application Key Flexfield	(FND_APP_KEY_FLEXFIELD

You must have access to the Application Implementation Consultant role in order to export or import setup data. However, access to additional roles is needed to export and import setup data for certain business objects:

Business Object Name	Required Role Name
Corporate Card Expense Type Mapping Rule	Corporate Card Administrator
Corporate Card Company Account	Corporate Card Administrator
Corporate Card Program	Corporate Card Administrator
Corporate Card Transaction Download Parameter	Corporate Card Administrator
Corporate Card Transaction Upload Rule	Corporate Card Administrator
Corporate Card Usage Limit Rule	Corporate Card Administrator
Bank Statement Reconciliation Tolerance	Cash Manager
Bank Statement Automatic Reconciliation Matching Rule Set	Cash Manager
Bank Statement Automatic Reconciliation Matching Rule	Cash Manager
Bank Statement Transaction Creation Rule	Cash Manager
Cash Transaction Type	Cash Manager
Bank Transaction Code	Cash Manager
Bank Statement Parsing Rule	Cash Manager
Bank Account	Cash Manager
Bank Branch	Cash Manager
Bank	Cash Manager
Collections Aging Bucket	Collections Manager
Collections Dunning Configuration	Collections Manager
Collections Preference	Collections Manager
Collector	Collections Manager
Incentive Compensation Participant	Incentive Compensation Application Administrator
Department	Human Capital Management Application Administrator
Legal Employer	Human Capital Management Application Administrator
Payroll Statutory Unit	Human Capital Management Application Administrator
Division	Human Capital Management Application Administrator
Job	Human Capital Management Application Administrator
Location	Human Capital Management Application Administrator
Enterprise Information	Human Capital Management Application Administrator
Legislative Data Group	Human Capital Management Application Administrator

Export Scope: Explained

Certain business objects contain export scope. These are typically the business objects that are qualifiers of other setup data and therefore, might potentially use filter or segment data during setup export and import. Some of the examples of business objects with scope are Business Units, Legal Entities, Ledgers, and Territories.

All setup data from all business objects in the export definition is exported by default. However, exported setup data can be filtered by specific export scope values if the business object has scope enabled for setup data export. During export, you will have the option to choose specific scope values. For any setup data where scope is applicable, only the data that matches the selected values will export.

FAQs for Importing and Exporting Setup Data

What's a setup business object?

A setup business object is a self-contained representation of a business entity supported by a setup task. These are logical representations of real-world objects. Setup business objects represent the data entered when you perform setup tasks. Business objects used by setup tasks also require web services to facilitate export and import of corresponding data. Setup data entered by way of a setup task is stored in the table associated with the corresponding business object. For example, Primary Ledger is the business object of the setup task called Manage Primary Ledger. When the Manage Primary Ledger task is performed, data entered is stored in the tables associated with the Primary Ledger business object.

What happens if I upload a different version of the same configuration package?

The previously uploaded version is overwritten with the newly uploaded version.

How can I export or import an implementation project without the associated setup data?

When you create a configuration package select the option to export the setup task list only. When this configuration package is exported and imported, only the task list from the selected implementation project will be transported.

What happens if I modify a configuration package that I recently created?

You can only modify configuration packages that display a status of definition in progress. The configuration package definition is locked once you submit it for export or upload it for import. If you want to keep making modifications to a configuration package you can save it until you are ready to submit it for export.

How can I see what setup data is transferred when I export a configuration package?

When you create a configuration package by selecting an implementation project, the business objects associated with the tasks in the implementation project task list are what will be included during export. You can view these business objects when you are working in the implementation project or after you create the configuration package.

How can I exclude any business objects from exporting or change the import sequences?

By default, all business objects related to the task list of the implementation project used in the configuration package will be exported. You can exclude any business objects from exporting by deselecting the business object from the default list. If you deselect a business object then the business object data will not be exported or be available for subsequent import. The default import sequences of the business objects are based on the order of the related tasks in the implementation project. You can change the import sequence when creating a configuration package. As a result, the order in which the business objects export and import changes. Use caution when excluding business objects or changing their import sequences because data dependencies among the business objects might exist, which could result in failures during import.

Why did the export process not raise any errors when it did not export any data?

Sometimes no data exports for a business object even though the process completes successfully without any errors. This happens when only Oracle Fusion Applications seeded setup data exists in the business object. Setup export and import excludes Oracle Fusion Applications seeded setup data. A message indicating that no rows were processed and no failures occurred during export will display when the export process completes.

Why did import errors appear when no data to import is found?

If your configuration package contains no data for a given business object, the import process sets the status to Completed with Errors and indicates that no data is found. The application is trying to ensure that all relevant data for a given implementation is available during the import. If data does not exist or you do not want to import data for the business object, you can bypass these errors by resuming the import process without pausing for errors.

When does export or import show errors at the data level as opposed to the system level?

An error at the business object level occurs if the setup export and import web services cannot be invoked. For example, if a service cannot be found in the specified location where it is registered or access is denied to the service then the application will raise an error. In general, errors occur at the system level. However, data level error may also occur depending on how the web services were designed.

What happens if my import process remains in the User Action Required status?

An import process is set to User Action Required when the process has paused because either an error occurred that you need to correct, or certain data must be imported using another application or process external to the Setup and Maintenance Work Area. Review the process results and resume the process once you have taken appropriate actions to correct the errors or externally imported the required data.

How can I view the associated business object hierarchy?

The task list generated for an implementation project not only drives the implementation tasks but also determines what setup data exports and imports during deployment to another instance. You can see the list of business objects representing the setup data by selecting the business objects view from the Manage Implementation Projects page. The business object view shows the business objects associated with the tasks and gives an insight into the order the business objects, and therefore setup data, exports and imports when you deploy the implementation to another instance.

How can I view and print any errors generated by an import or export process?

Download and then view or print the Export Results Report or the Import Results Report for the relevant process.

How can I cancel an export or import process that I submitted?

You can cancel any export or import process from the Mange Export and Import Processes page or from the Manage Configuration Packages page. Select the process you want to cancel, and choose Cancel Process from the Actions menu. Once you confirm to cancel the process, it will complete processing of the business object that already started and will not process the remaining business objects. The process status will be changed to Canceled and you will not be able to resume the process.

When does it make sense to create multiple configuration packages from the same implementation project?

You can use the same implementation project to create many configuration packages. It is only useful to do so if the list of tasks in the implementation project has changed, or tasks and their associated business objects in the selected implementation project define the setup export or import definition for the configuration package. It is also useful if you use a custom export or import definition for different configuration packages.

Why does the configuration package contain some scope values by default?

If you have selected any scope values when performing an assigned implementation task, then the selected values are preselected as candidates for filtering setup during export and import. Some application core tasks, such as tasks for defining profile options, have parameters defined that you can use as setup filters and are preselected as filter candidates for export and import. You can remove any of these preselected values when you are creating the configuration package. You can also add more scope values for export and import purposes only.