Skip to main content

Hello,

We have like many other customers developed our own Oracle objects including PL/SQL APIs to be used alongside the IFS Customisations.

For example, we have a custom event that fires on a specific action which then submits a background job to call and process code within a custom PL/SQL API. If we need to perform a modify or creation of data within IFS, then we ensure to use the standard IFS API calls wrapped within the custom API.

No one seems to be able to give clear guidance on what is and isn’t allowed with regards to the IFS licensing options. 

For example, if we were to use ASFU license from IFS can we continue to utilise our custom Oracle objects that have been developed over the years?

We understand if we were to go down the Oracle Enterprise route, all restrictions are effectively removed.

Please can advise be provided 

Thanks in advance

Shaun

Hi @SHAUN_KERSLAKE,

Technically speaking you should be able to keep using your custom API’s even with ASFU license model as long as they are used explicitly for IFS and not other applications. There is definitely no hard restriction in ASFU license to block out any custom code. They would pretty much be customizations done to extend the standard product features so there wouldn’t be any any difference from a IFS delivered customizations. 

The ASFU restrictions come in only if you are thinking of running a completely different application that uses Oracle as a backend. This is a big no no as the ASFS - IFS license will only cover IFS installations and you would get in trouble if for some reason Oracle decides to do a license audit.  

Cheers. 

Whilst going through an IFS Upgrade we had the same query.

Here is some information provided by IFS:

 

Oracle DB ASFU and modifications/integrations and 3rd Party Products

The functional scope of the usage must be limited to the functional scope licensed from IFS

1)         It is allowed to customize a function or the functional scope to fit the need of a customer usage scenario, but it may only be done within the functional scope of the licensed software. Consequently, it is not allowed for the customer to license only some functionality from IFS and instead develop customizations to achieve the functionality or business processes that are the same or overlapping with functionality in other parts of IFS’ standard offering. Nor may the customer build and run a completely new and/or independent function or business process.

 a)        Example 1:  A customer may not license IFS Applications without the IFS Quality Management module and instead build a separate quality management module as a customization

b)         Example 2:  A customer may not license IFS Applications Finance solution and build a Hotel booking system as a customization

c)         Example 3:  It is allowed to add functions for the sole purpose of being called from IFS configuration artefacts, like custom menus, customer event actions, etc provided the function is within the functional scope of the licensed software.

2)         It is not allowed for customer to let any 3rd party product to run its proprietary business logic and/or storage in the Oracle ASFU DB

3)         3rd party products may be integrated with IFS Applications:

a)         By accessing IFS Applications using any of the integrations methods described in the “IFS Administration & Configuration Guide -> Integration” section of the IFS Applications Technical documentation, and/or by using the IFS Access Providers.

b)         By reading data directly from the database through ODBC/JDBC (or similar access methods). It is, however, NOT allowed to writedata directly to the database through ODBC/JDBC (or similar access methods).

c)         Through Database Links as described here: http://docs.oracle.com/cd/B28359_01/server.111/b28310/ds_concepts002.htm#ADMIN12083

The IPR of the code regarding customizations in the database layer must belong to IFS or the customer (end-user).

4)         The purpose of the Oracle DB ASFU agreement is to allow customers (end-users) a lower cost alternative when opting to limit the use of Oracle to IFS Applications only. The solution may be customized to better fit the business need as described above. The IPR of a customization made in the database layer (data model changes, PL/SQL business logic or APIs) must however belong to IFS or the customer (end-user) as follows:

a)         IFS ownership:

a1)        Where IFS has developed the customization

b2)       Where the customization incorporates or is a derivative work based on any IFS proprietary code.

b)         Customer or IFS ownership, to be agreed: Where the customization has been developed by customer or a third party on a standalone basis, i.e. not incorporating or being a derivative work based any IFS proprietary code(“Standalone customizations”).

c)         Customizations developed by 3rd parties:

  • c1)        In view of the above, any 3rd party (IFS partner or other) that integrates to IFS and need to modify IFS in the database layer must assign the IPR of such a modification to IFS.
  • c2)        PLEASE NOTE: In order for ownership in standalone customizations in the database layer to be placed with the developing 3rdparty, the customer must have a full use Oracle DB license.

5)         Any integrated 3rd party product must carry its own DB license.

Terms & ConditionsCookie settings