Hi everyone,
Current IFS version: IFS apps 9 EE
Target IFS version: IFS cloud 23R2 (hosted on prem by us)
Today in IFS9 we have several applications (built by us) that are connecting to our database directly to “interface” with IFS. We have several oracle users that handle these connections, created as IFS fnd users. These users are granted access to the database API package methods via permission sets, and are set as inactive in the IFS application as they never actually log into the app and the oracle user handles everything.
Example: User logs into non-IFS app and enters information about a purchase order. That application connects to the database hosting IFS as an appropriate oracle user, calls {app_owner}.purchase_order_api.new and creates the purchase order.
We are in the process of upgrading to IFS cloud. In IFS cloud this presents us with two issues: Oracle users backing IFS fnd users are removed and permission sets are no longer mapped to oracle roles. We attempted to remove the section in the upgrade script which drops all the Oracle users, but each time upgrading from say 22R2 to 23R2 the users are dropped again. It appears the direction that IFS wants us to take is to utilize the projection REST APIs as opposed to direct DB access.
There are downsides to this that we can see however, such as losing the control over transactions / error handling that we have with doing things directly in the database, the lack of being able to specifically call the database methods we need, as well as the overall time it will take to convert to this new way of doing things.
Have any others that have upgraded to IFS cloud faced this, and what were your resolutions / lessons learned?
Any other suggestions to consider on the above would be greatly appreciated.
Thanks,
LEdwards