My Oracle Support Banner

Duplicate Licenses Assigned To A Transaction Line (Doc ID 2539664.1)

Last updated on MAY 06, 2022

Applies to:

Oracle Global Trade Management Cloud Service - Version 6.3.4 and later
Information in this document applies to any platform.


When running a compliance rule screening on a transaction line through a GTM agent process, when doing another compliance rule screening to the line, sometimes GTM assigns a duplicate license to release previous control code again.

The issue can be reproduced at will with the following steps:

1. Manually create a transaction in GTM
2. GTM does validation against the item
3. GTM proceed a compliance rule screening (1st time), that puts a control code (e.g. CONTROL-CODE-A) at the transaction line level – it is then on hold.
4. GTM tries to release the above control hold by assigning a license (1st time).
5. GTM checks whether the license process successfully released the transaction line. If yes, then a direct sql update is used to create a new GTM license in the system, the license is based on the transaction (license number same as the transaction ID, license available quantity is retrieved from transaction line quantity, the license is designed to release a specific control code – e.g. CONTROL-CODE-B)
6. GTM continues to run a compliance rule screening (2nd time), that may put a control code (yes, CONTROL-CODE-B) at the transaction line (so as of now, the line may get 2 control codes on it, but remember the control CONTROL-CODE-A already released in previous step).
7. GTM tries to assign license to the transaction (2nd time). It is expected to use the new license created in previous step and release the control CONTROL-CODE-B.




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.