Dear @Indrasan Yadav,

As per the discussion with @Hassan Abdine :

In NE License Management, the License Identifier Key is used to ensure license uniqueness. This key is a combination of the following attributes:
Object ID + License ID + License Details

Example 1:
The unique identifier key is: "RIYA2U6760B-P3_LT1S0000RB00_RESOURCE BLOCK(FDD)" for both licenses.
Example 2:
The unique identifier key is: "DM1MBSCH01_LQW1CS01_Voice Erlang-Erlang" for both licenses.

Therefore, the uniqueness of the licenses will be lost, making it difficult to update data or detect duplicates.

Regards,
Mustapha Al Hage

Dear @Mustapha Al-Hage,

Thank you for your clarification.

I noticed that the JIRA status is currently paused. Could you please resume it so we can proceed with closing this JIRA?

Additionally, I will create a separate JIRA to update the rule in FRS to make the LIC ID unique and ensure it will import in NEP accordingly.

Thank you
Indrasan

Cancelling this JIRA as I will create a separate JIRA (ZKU-264) to update the rule in FRS to make the LIC ID unique and ensure it will import in NEP accordingly.

As per NEP-DEV current LIC identifier is Node ID_LIC ID_LIC details so if my requested condition will be implement then it's difficult to identify duplicity & related errors.