ADF Integration is Installed with an Incompatible Installer

When installing the ADF Desktop Integration add-in an error similar to the following occurs:

"ADFDI-04000: ADF Desktop Integration is installed on this computer with an incompatible installer. Please uninstall the currently installed version and retry the installation with the new installer."

The message may vary:

• "Oracle ADF 11g Desktop Integration Add-In for Excel has previously been installed on this computer with an incompatible installer. Please uninstall it and retry the installation."
• "ADFDI-04000: Oracle ADF 11g Desktop Integration Add-In for Excel is installed on this computer with an incompatible installer. Please uninstall the currently installed version and retry the installation with the new installer."

Reproduces starting in ADFdi 11.1.1.7.3 (4.0.0) - available in FA Release 9

Cause:

The ADF Desktop Integration add-in was previously installed with a legacy installer that is not compatible with the standard installer (adfdi-excel-addin-installer.exe).

Solution:

A. Remove the previous ADF Desktop Integration add-in installation with "Add/Remove Programs":

1. Open "Add/Remove Programs" in the Windows control panel
2. Search for "ADF Desktop Integration" and remove any installed versions of the client
3. Retry the installation with the standard installer (adfdi-excel-addin-installer.exe)

B. If the ADF Desktop Integration client is not present in the installed programs listed in "Add/Remove Programs":

1. Open Excel and navigate to Excel options
2. Click the "Add-Ins" category
3. In the "Manage" dropdown menu select "COM Add-Ins" and click "Go"
4. "Oracle ADF Desktop Integration Runtime Add-In for Excel" or ""Oracle ADF Desktop Integration Add-In for Excel" should be present in the list of add-ins. Select it with the checkbox and click "Remove".
5. Retry the installation with the standard installer (adfdi-excel-addin-installer.exe)

Source:

ADFDI-04000: ADF Desktop Integration is installed on this computer with an incompatible installer. (Doc ID 2017956.1)

Workaround for Maintain Transaction Class Deposit in Fusion Receivables

As we know there are no transaction class deposit in Fusion Receivables.

According to this Doc ID:

1. Is There An AR Transaction Class = Deposit And AR Transaction Type = Commitment In Fusion Receivables ? (Doc ID 2052222.1)
2. What are the Workarounds for Customer Deposits and Bank Guarantees in Fusion? (Doc ID 1675045.1)
3. Oracle Fusion Receivables: Transactions Workbench Issue: Cannot create Deposits/Guarantees (Doc ID 1313616.1)

Detail below:

Doc ID 2052222.1

APPLIES TO:

Oracle Fusion Receivables Cloud Service - Version 11.1.9.2.0 and later
Information in this document applies to any platform.

GOAL

Is there an AR transaction class = Deposit and AR transaction type = Commitment in Fusion Receivables ?
 

SOLUTION

No, there is nothing like that in Fusion. For deposit use receipts
 

REFERENCES

Doc ID 1675045.1

What are the workarounds for deposits and guarantee transactions in Fusion Applications?
 

SOLUTION

Possible workaround - For Customer Deposits:
===================================

For Customer Deposits when you receive an amount from your customer which needs to be tracked against the subsequent invoices or kept open . The amount held under this document is considered in calculating the customers outstanding balance.

1) On receipt of a deposit from your customer - Create a Receipt ( may be
 use a separate receipt method to be able to track such receipts).

2) Apply the invoices raised to such receipt to have the effect of squaring off the deposit amount against the invoice . (In EBS you would have raised the invoices against the deposit)

There is no known workaround for bank guarantees.

An enhancement request has been logged.
 

Bug 13920845 FUSION RECEIVABLES NEED DOCUMENT TYPES FOR CUSTOMER DEPOSITS , BANK GUARANTEES

REFERENCES

NOTE:1313616.1 - Oracle Fusion Receivables: Transactions Workbench Issue: Cannot create Deposits/Guarantees

Functionality of Segment Value Inheritance ESS Process

The Segment Value Inheritance process simplifies the maintenance of the chart of accounts. When the characteristics of values in the value sets are updated then all previously created account code combinations that referenced such values are not automatically updated by these changes.

This process is run to automatically propagate the following attributes of a segment value to all account code combinations which contain that segment value.

- Enable/disable flag
- Effective dates
- Allow budgeting flag
- Allow posting flag

The Segment Value Inheritance process allows you to run a controlled process to update such existing account code combinations. This process maintains and corrects the current attribute settings for those account code combinations that contain the account values that were changed.

For account code combinations where the present settings need to be retained and not impacted by account attribute changes, activate the flag to preserve the account code combination's attribute. Activating the flag prevents those account code combination's attributes from being update when the Segment Value Inheritance process is run.

Note:

• Use the Segment Value Inheritance Exception Report to view the account combinations that have been changed.
• Individual segment value attributes override account combination attributes.
• Conflicting settings for Enabled, Allow Posting, From Date, or To Date are resolved by using the most restrictive of the settings of the individual segment values.
• Disabling a segment value disables the combinations containing that value, even if the Preserve Attributes check box is selected