Issue Summary:

The ticket raises concerns about instances where different APP_ENTITLEMENT_NBR share the same APP_ENTITLEMENT_ID.

The partner who initially reported the issue asked about the underlying cause, questioned if it is a bug, and inquired about the potential reuse of identifiers for different licenses.

After an initial investigation, it was concluded that this seems to be a bug at source that caused the issue while migrating the license from CCP to HAMS.

Steps to Reproduce

1. N/A
2.  

Expected Results

The migration of licenses from CCP to HAMS should maintain consistent identifiers, ensuring that each APP_ENTITLEMENT_ID is uniquely associated with a single APP_ENTITLEMENT_NBR. This consistency is crucial to prevent any confusion or mismanagement of licenses during and after the migration process.

Actual Results

During the migration from CCP to HAMS, instances were observed where the same APP_ENTITLEMENT_ID was associated with different APP_ENTITLEMENT_NBR values. This discrepancy indicates a potential bug in the migration process, leading to confusion and potential mismanagement of licenses.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available