Denied Party Incremental Content Creating a New Data Version
(Doc ID 1551495.1)
Last updated on FEBRUARY 25, 2019
Applies to:Oracle Global Trade Management - Version 6.3.0 to 6.3.2 [Release 6.3]
Information in this document applies to any platform.
After downloading and processing the trade content for Item Classification and Denied Parties, the Denied Party Data is coming incrementally. This means that every new update in Customs Info file is incrementally sent to GTM. However, once a new increment comes, a new data version is created with IS_CURRENT flag set for this data version as 'Y' and for all other Data Versions of Restricted Parties as 'N'. This leads to the problem that when we screen records upon receiving new incremental updates, it is screened against the incremental trade content and not whole content. This defeats the purpose of screening. All parties need to be creened if complete trade content is changed, ie when a new data version is created. Hence, every time there is an incremental update, at present system is screening all the Contacts Master (huge volume) and that too against the incremental content (with current data version). The results are therefore incorrect as well as this takes unnecessarily long time to screen all contacts.
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