The content of licensed LTU role [FND_WEBENDUSER_B2B] has been modified in Apps10

Hi ​@CorVenkaP ,

   This does not look like an expiration or user-count problem, because your license is still valid until 2030-03-26, your full-user usage is 62/65, the LTU usage is 15/15, and the specific violation shown is:

The content of licensed LTU role [FND_WEBENDUSER_B2B] has been modified

That message points to a licensed permission set content change, not to simple overconsumption. In other words, IFS is detecting that the delivered LTU role FND_WEBENDUSER_B2B no longer matches the licensed definition.

What it usually means

In Apps 10, licensed LTU/ATU permission sets are expected to remain as delivered. If someone has:

• added permission sets to FND_WEBENDUSER_B2B,
• removed grants from it,
• copied content into it,
• or otherwise changed the role contents during/after the UPD29 deployment,

IFS can flag the license state as invalid with exactly this type of message.

What to check

1. Compare FND_WEBENDUSER_B2B in your environment against the delivered UPD29 definition.
2. Check whether any custom grants, projections, pages, or permission sets were added to that LTU role during retrofit or post-upgrade security changes.
3. If you need extra access for those users, do not modify the licensed LTU role directly. Instead, keep the delivered LTU role intact and assign additional custom permission sets separately to the relevant users.
4. Re-run the license validation after restoring the role content.

Practical resolution

The safest fix is usually:

• restore FND_WEBENDUSER_B2B to the standard delivered content for UPD29,
• move any customizations out of that licensed role into a separate custom permission set,
• then refresh/revalidate license information.

One more thing to keep in mind

  There are also cases where Apps 10 can show license-invalid messages because of middleware/server connection issues rather than a true license defect. In one Apps10-UPD21 community case, the license was still valid and the issue cleared after server-side intervention/restart. So if the LTU role content is actually unchanged, it is worth checking middleware/server logs as well.