- Flexera Community
- :
- FlexNet Manager
- :
- FlexNet Manager Suite Known Issues
- :
- Known Issue: Users with expired responsibilities consume Application User licenses for Oracle EBS ap...
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
The content you are looking for has been archived. View related content below.
Known Issue: Users with expired responsibilities consume Application User licenses for Oracle EBS applications (IOJ-2093927)
Known Issue: Users with expired responsibilities consume Application User licenses for Oracle EBS applications (IOJ-2093927)
Description
The queries used to determine active users from Oracle EBS are not taking expired responsibility into account and users bound to the expired responsibility consume the license.
Replication Scenario
Check if there are expired responsibilities on the Oracle EBS.
Workaround
Remove expired responsibility from the EBS system. Alternatively, it is possible to manually override/exempt the consumption to account for this.
Fix status
This issue is under consideration to be addressed in a future FlexNet Manager Suite release.
Other information
Affected components: SAM for Oracle, Software license management
Master issue ID: IOJ-2093927
Also known as: FNML-76688
Tip: If you have been impacted by this issue, please click the KUDOS button above. This helps to track the relative significance and importance of issues. Clicking on an option against "Was this article helpful?" also helps assess and improve the usefulness of content.
- Mark as Read
- Mark as New
- Permalink
- Report Inappropriate Content
Is there any update to delivering a bug fix for this issue?
- Mark as Read
- Mark as New
- Permalink
- Report Inappropriate Content
@danbeckner - at this point in time this issue is under consideration to be addressed in a future FlexNet Manager Suite release. As the status changes it will be reflected in "Fix status" section of the article above.
- Mark as Read
- Mark as New
- Permalink
- Report Inappropriate Content
@ChrisG Thanks! We actually just met with @jborchers and he noted the product development team is planning to release a fix in an upcoming ARL release which is great news!