Cloud Documentation
Advanced Search


Using Common Features for Oracle Applications Cloud
Close Window

Table of Contents

Show All | Collapse

4 Data Management

Desktop Integration for Excel

Setting Up the Integration: Points to Consider

To use a desktop integrated Excel workbook to create or edit records that you can upload to Oracle Fusion Applications, you must fulfill software requirements, install a desktop client, and set up Microsoft Excel.

Software Requirements

You must have installed:

  • Microsoft Excel 2007 or 2010
  • Microsoft Windows XP Professional, Vista - Business, Vista - Ultimate, or 7

Desktop Client Installation

Install the Oracle ADF Desktop Integration Add-in for Excel, which is a desktop client that enables you to use the integrated workbooks that you download from Oracle Fusion Applications. If the client installer is not available under Navigator - Tools, then ask your administrator where you can find the installer.

Important

Make sure you are signed in to your computer with your account when you perform the installation. For example, you cannot have someone else sign in as an administrator and make the installation available for all users of your computer.

Depending on the setup of the client installer itself, you may get automatic updates when new versions of the client are available. If you do not get automatic updates, then you need to reinstall the client whenever the client version changes. You can find your client version in the About section of the workbook and ask your administrator if that version is the latest.

If the location of the client installer ever changes, then:

  • You will not receive automatic updates.
  • You must uninstall the client from your computer and use the installer from the new location.

Note

Any time you need to reinstall the client, you must first uninstall and then perform the install procedure again.

To uninstall, use the Add or Remove Programs dialog box from the Control Panel to remove the Oracle ADF Desktop Integration Add-in for Excel client.

Microsoft Excel Setup

Perform the following steps in Microsoft Excel only once, even if you reinstall the desktop client.

  1. Click the Microsoft Office button, and click the Excel Options button.
  2. In the Excel Options dialog box, select the Trust Center tab, and click Trust Center Settings.
  3. In the Trust Center dialog box, select the Macro Settings tab, and select the Trust access to the VBA project object model check box.

Note

The exact steps can vary depending on your version of Microsoft Excel.

Working in Desktop Integrated Excel Workbooks: Points to Consider

Where available, you can download a desktop integrated Microsoft Excel workbook in which you can create or edit records. While you work in the integrated workbook, no changes are actually made in Oracle Fusion Applications; your edits take effect only after you upload the records back. As you work, keep in mind conventions and statuses used in the file, requirements for search, possible need to refresh, and things you should not do.

Conventions

Some column headers in the integrated workbook might include [..]. This means that you can double-click or right-click within any cell in the column to open a dialog box that lets you select a value to insert into the cell.

Statuses

The worksheet status in the header area applies to the entire worksheet, or tab, within the integrated workbook. Likewise, the table status applies to only the corresponding table. The row status applies to the state of the row within the workbook, not to the record itself. For example, if the row is an expense item, the status does not mean the status of the expense item itself, but of the data in the row, in the context of the workbook.

Search

Some integrated workbooks have search functionality. For the search to work within the workbook, you must sign on to Oracle Fusion Applications.

Refresh

After you upload to Oracle Fusion Applications, you might need to refresh the data in the table if your changes are not reflected. You can use the refresh option for the table, or perform a filter or search on the table.

What You Should Not Do

To make sure that the upload to Oracle Fusion Applications goes smoothly, do not:

  • Rename text from the integrated workbook, for example the worksheet or tab names.
  • Use your own styles in the file.
  • Add columns.
  • Delete any part of the template, for example columns.
  • Hide required columns and status columns or headers.

Troubleshooting the Integration: Procedure

The integration of Oracle Fusion Applications with Microsoft Excel allows you to download a desktop integrated workbook, create or edit records in the workbook, and upload the records to Oracle Fusion Applications.

Issue

The integration is not working. For example, you get an error when you try to open the workbook that you downloaded from Oracle Fusion Applications, or the workbook t is not rendering properly.

Resolution

Check the version of the Oracle ADF Desktop Integration Runtime Add-in for Excel client that you currently have, and ask your system administrator whether you need to reinstall it. Find the version in the About section of the workbook.

If you have the correct version, then in Microsoft Excel:

  1. Click the Microsoft Office button, and click the Excel Options button.
  2. Select the Add-Ins tab, and check if Oracle ADF Desktop Integration Runtime Add-in for Excel is in the Inactive Application Add-ins or Disabled Application Add-ins list.
  3. If Oracle ADF Desktop Integration Runtime Add-in for Excel is in the Disabled Application Add-ins list:
    1. Select Disabled Items in the Manage field and click Go.
    2. In the Disabled Items dialog box, select oracle adf desktop integration runtime add-in for excel and click Enable.
    3. Back in the Excel Options dialog box, select COM Add-ins in the Manage field and click Go.
    4. In the COM Add-Ins dialog box, select Oracle ADF Desktop Integration Runtime Add-in for Excel.

    If Oracle ADF Desktop Integration Runtime Add-in for Excel is in the Inactive Application Add-ins list, then perform only steps 3.3 and 3.4.

  4. If Oracle ADF Desktop Integration Runtime Add-in for Excel is in the Active Application Add-ins list, then contact your help desk.

Note

The exact steps can vary depending on your version of Microsoft Excel.

FAQs for Desktop Integration for Excel

What's the difference between export and Oracle ADF Desktop Integration for Excel?

Use the Export button or menu option to download data to view or analyze. You get a Microsoft Excel file, of any type that Excel supports, containing selected or all records from the corresponding table. If row selection is disabled, then the export would include all rows. When all rows are exported, that includes all the rows that are not visible on the page. However, any search criteria, filters, and Query By Example values applied to the table can exclude rows from the export. Data from hidden columns are also not included in the export.

Use Oracle ADF Desktop Integration for Excel to create or edit records in a Microsoft Excel workbook and upload the records back into Oracle Fusion Applications. This feature is helpful for mass updates or working outside of Oracle Fusion Applications. In most cases, you download the desktop integrated workbook from a link in the regional area, for example the Create Expense Items in Spreadsheet link, or from a table, for example using the Prepare in Spreadsheet button. The workbooks downloaded from a link can include rows of data, or empty rows except for default values in some columns. From a table, what is included in the workbook is determined the same way as for the export option. If no rows are selected, however, the workbook does not include any records from the table.

Note

If you are using a feature integrated with Oracle Fusion Applications that presents a set number of rows per page or view, then exporting or downloading all rows might not include all the data you want. You might need to navigate to subsequent sets of rows to export or download.

FAQs for Attachments

How can I delete attachments?

Use the Delete icon button if available. If not, that means there are no attachments or more than one attachment for the object. When the Delete icon button is not available, use the Manage Attachments icon button to open the Attachments dialog box and delete specific attachments.

Audit

Audit History: Explained

Using audit history, you can view the changes that the application data underwent. It provides you with details of the business objects that were created, updated, and deleted. You can select among several search parameters to decide the type of audit history report that you require. To view the history or to create a report, you require special access rights to the application. To access the Audit History work area, click Audit on the Navigator menu of Oracle Fusion Applications.

Report Summary

Audit history search results appear based on the parameters selected. A summary of the audit history appears in the search results table displaying key data such as date, user, event type, business object type, and description. If you need more details, you can search again with modified search criteria to get a detailed report. You can export the report summary to Microsoft Excel.

Detailed Report

The detailed audit history report appears when you use additional search criteria. This table shows how the search criteria affects the search results.

Search Parameter Result of Selection

Business Object Type

Note

This parameter is applicable only for the business objects that belong to Oracle Fusion Applications.
  • Narrows the search results to that specific business object within the selected product.
  • Enables the Show Attribute Details check box.

Include Child Objects

Displays all the child objects that were listed under the business object when audit was set up. For example, a sales order object that contains several items as child objects.

Note

Only the objects at the immediate parent-child level are displayed. To view the children at subsequent levels, select the child object as the business object type and search again.

Show Attribute Details

  • Displays the name of each attribute that was either created, updated or deleted, and the old and replaced values.
  • Enables the Show Extended Object Identifier Columns check box.

Show Extended Object Identifier Columns

Displays the instances (contexts) in which the business object was used. The context values specifically identify the objects and the transactions in which they were used. Each context is unique and assigns a unique description to the business object.

You can export the detailed report to Microsoft Excel.

Note

The default report displays a standard set of columns that contain prominent details of the audit history. To view additional details, you can customize the display of columns.

Audit Event Types: Explained

Events trigger the audit process, and the details pertaining to that event are stored in the audit table. When you view audit history, you can view which events triggered the changes to the object data during a specific period of time. However, for events to trigger the audit process for the business objects, it is necessary that the objects must have been selected and enabled for auditing during audit setup.

For Oracle Fusion Applications, transactional events that monitor the create, update, and delete operations trigger the audit process. The attributes of the audited object data can be used in lookups and foreign keys to display values in the audit history. Oracle Fusion Applications supports displaying the audited information as per the application's language settings.

For Oracle Fusion Middleware products, events such as failed login attempts that are used as triggers, store the information in sandbox in absence of an audit table. The audited information is presented only in English.

Note

This topic focuses on the event types available in Oracle Fusion Applications. For details on events used in the Oracle Fusion Middleware products, refer to the Oracle Fusion Middleware documentation.

Create Operation

This event triggers audit activity whenever business object data is created and stored in the database. As a result, the name of the created object, the name of the user who created the object, the time stamp, and other details are stored that appear in the audit report.

Update Operation

This event triggers audit activity whenever existing business object data is updated. As a result, both the old and updated values of the object, the name of the user who updated it, the time stamp, and other details are stored that appear in the audit report.

Delete Operation

This event triggers audit activity whenever existing business object data is removed from the database. As a result, the last value that the object attributes contained, the name of the user who deleted the object, and other details are stored that appear in the audit report.