About the Change to the Accounts Payable Extension at Version 13

If you are installing FinancialForce Accounting for the first time at version 13 you do not need to read this section. It describes how this change affects organizations that have already installed an earlier release of FinancialForce Accounting and an earlier release of the FinancialForce Accounts Payable Extension (ffap).

In versions of FinancialForce Accounting before version 13, the Extended view of payable invoices and payable credit notes was only available by installing an extension package. However, in this release the code and triggers for this have been integrated into the core FinancialForce Accounting application.

How does this affect me?

In the vast majority of cases you do not need to do anything and your application will continue to work as expected.

This is the case when:

You have a new installation of FinancialForce Accounting V13. In this situation you do not need to install the V13 FinancialForce Accounts Payable Extension (ffap). In fact, you should not install the ffap extension against a fresh install of FinancialForce Accounting V13.

You have an older version of FinancialForce Accounting but you have never installed the corresponding FinancialForce Accounts Payable Extension. Classic Edition is unaffected by this issue.

You have upgraded from an older version of FinancialForce Accounting to version 13 and also to the latest FinancialForce Accounts Payable Extension.

In this situation, you must upgrade latest accounts payable extension package and the core application together and in the following order:

1. Install the FinancialForce Accounting (c2g) package V13.
2. Install the FinancialForce Accounts Payable Extension (ffap) package V12.1 or later.
3. Install the FinancialForce Accounts Payable Extension (ffap) package V13.

Note: Note

If you have customized the ffap manage lines fieldsets, you will need to make the same customizations to the equivalent fieldsets installed by the core (c2g) package.

There is a new custom setting that becomes significant in this scenario. This custom setting is described in Extension Settings.

Why is there still a FinancialForce Accounts Payable Extension package at this release?

As we said earlier, the code and triggers in the old Account Payable Extension package (ffap) have now been moved into the core package (c2g). However, because some customers have customized code and page layouts it was not possible to immediately remove the schema (the object and field definitions) from the ffap extension package.

When you upgrade to FinancialForce Accounting version 13 (and also to the corresponding FinancialForce Accounts Payable Extension) the application will, by default, continue to reference the ffap fields in the new extension. At this point everything should now work correctly and as expected.

This default behavior is controlled by a new custom setting described in Extension Settings. In most cases you should leave this at its default (false).

Can I stop using and remove the new FinancialForce Accounts Payable Extension package?

Yes you can, but you need to perform a number of steps before you can do this safely. Remember, the code in the core application is looking to the fields in the extension package when values for some fields are derived.

To be able to remove the extension package you must

Adapt your code to use the fields and fieldsets in the core application instead.

Select the custom setting to tell the application to stop using the fields in the accounts payable extension.

If you want to continue operate in Extended Edition, assign the new 'extended' page layouts to your users.

If you have customized the accounts payable page layouts you will need to customize the new 'extended' ones to point to the fields in core (c2g).

If you have created your own page layouts, you will need to make the same customizations to the new c2g ones.

Test your new or customized page layouts.

Only now can you consider removing the accounts payable extension package (ffap). If you've performed all the steps correctly, the ffap fields are no longer referenced and the package can be uninstalled. This is optional.