Restrictedpartyscreening

TRADE COMPLIANCE M ANAGEMENT
If you have any questions or comments about this topic or the online help, please contact us.
About Restricted Party Screening

Related Topics
Oracle Global Trade Management (GTM) is a global trade automation platform that enables
companies to optimize and streamline business processes related to cross-border trade. With well-
structured compliance policies and trade automation tools to help implement and enforce those
policies, companies can achieve best practices in global trade both within and outside of their
organizations. Restricted party screening is one of the processes used to support trade compliance.
GTM’s Restricted Party Screening (RPS) services enable companies to perform screening of
parties, trade transactions, and so on to ensure compliance with international shipping policies.
The United States of America and other regional, unilateral, and multilateral agencies enforce
regulations which restrict businesses and people from conducting trade with specific foreign entities
(individuals, companies, countries). These entities are referred to as Denied, Debarred, and/or
Restricted Parties (“Restricted Parties”). Examples of these entities include but are not limited to
known terrorists, organizations that fund terrorists, and parties guilty of trade violations. Typically,
the restricted parties are mainly countries subject to embargoes, and persons, businesses, and
organizations subject to financial sanctions. Periodically, these agencies publish lists of entities that
are marked as restricted parties.
In order to adhere to the regulations, companies screen their party master data and transactions
against these lists, which can be very time consuming and laborious. Furthermore, if a business
ships goods to a restricted party, it could incur fines, penalties, and ultimately the loss of export
privileges.
GTM offers a configurable solution to screen parties against a list of restricted parties. Parameters
can be configured to optimize potential match results. The screening engine can be called at any
point in a business process. You can screen parties at the time of party creation, which ensures
they are cleared for compliance when transactions occur. You also have the option in GTM to
screen parties at the time of transaction to ensure compliance. The following are the steps involved
in the process of restricted party screening:
1. Data Content Source : Different government authorities release regular updates on various
data content lists for compliance purposes. These government updates are regularly
processed into a structured form by different content providers (for example, Descartes) to be
consumed and utilized by different companies. GTM content source helps companies to
define the type of content (e.g. Restricted Party List, Product Classification, etc.) you want to
download and access from different content providers. In addition, the content source defines
how the content is downloaded including protocols such as HTTP, FTP, etc.
Note : The preferred content provider for GTM is Descartes.
2. Download Data Content : This process enables you to download various trade content data
to GTM, based on a data content source definition. You can trigger the download instantly or
define a schedule for automatic downloads of data content at regular intervals.
3. Configure Screening Parameters : You can configure screening parameters to screen
parties/contacts against the lists of restricted parties. GTM provides you with options to
determine the potential matches based on matching engine (like keyword, dice engine),
attributes for matching, threshold, and weighting of the overall matching. Additional
parameters include exclusion lists, punctuation marks, etc.
4. Perform Screening : You can perform the screening in two different ways. First, you can
perform an ad hoc screening before entering a party into the party manager in GTM. Second,
you can perform restricted party screening based on parties, trade transactions, or
declarations. In this case, you can identify the potential matches and review them before
proceeding. You can perform multiple screenings on a party to meet different business needs
(for example, restricted party list screening, red flag screening, debarred country, etc.).
5. Review Screening Results : Once screening has been performed, you can view the
restricted parties that might potentially match with your parties and determine whether you
can conduct business with the party or not. There are multiple user interfaces (UIs) in GTM
that enable you to perform this action. In addition, the Restricted Party Workbench and Work
Queues are provided which enable you to quickly and efficiently review the screening results
if you are working in environments with a high volume of parties.
Related Topics
Global Trade Content
Screen Service Configuration
Screening Restricted Parties
Restricted Party Screening Resolution
Match Engines
GTM Transfers of Information (TOIs)
Copyright © 2001, 2016, Oracle and/or its affiliates. All rights reserved.
For the latest installation and reference guides, go to the Oracle Technology Network (OTN) . For the proprietary guides
and training materials, see Knowledge Document 796594.1 on My Oracle Support .
For questions about Oracle Transportation Management or Global Trade Management, contact Support at
https://support.oracle.com or find the Support phone number for your region at
http://www.oracle.com/support/contact.html .
If you have any questions or comments about this topic or the online help, please contact Documentation .
TRADE M ASTER DATA

Related Topics
Global trade practice requires companies to have access to and use the current trade data
available. There are many types of trade data available with various sources, both nationally and
internationally. Failure to use the most up-to-date data can result in inaccurate screenings which
may lead to significant fines and penalties, delays, revocation of trade privileges, and lost revenues.
Examples of trade content include, but are not limited to:
x Denied Party Screening Lists

x Harmonized System and Classification Information
x Tariff and Duty Rates
x Binding Rules and Regulations
x Free Trade Agreement Information
Follow the steps below to download your data content:
x Content Source Configuration

x Download Data Content
x Restricted Party List
x Restricted Party Exclusion List
x Purge Data Content
x Purge Data Version
Related Topics
About Global Trade Intelligence
TRADE M ASTER DATA
GTM Content Source

Content Source Data Type | Configuration | Related Topics
This page is accessed via Trade Master Data > Power Data > Data Loading > Content
Source .
Use this page to define the list of the countries and trade data being supported, the details of the
content received from an external source, and how it is mapped to the GTM structure. You can
record information about your external sources of licensing, screening, and classification content.
Your system will use this information when it is time to update your content files. In this page, you
can capture the content type as well as the external system and communication protocol detail.
GTM ships with a public content source called “Descartes” that you can use to download data
related to restricted party screening and product classification. If there is a data type you want to
use that is not listed but is supported by Descartes, you can add it to the public content source.
On the Content Source UI, the Content Source Data Type grid must be configured with the details
of what you want to download. The Source Data Type field is the data type ID provided by the
external provider such as Descartes. The Content Type field identifies the type of content (HTS-US,
ML-US, RESTRICTED_PARTY, etc) to be downloaded. The "Supported" flag can be used to turn
on or turn off the subscription for that data type. The system will only download files for those data
types that have a check mark to indicate they are turned on.
At the bottom of the Content Source UI, the Configuration grid must be configured with the external
system location and communication method (for example HTTPPOST) indicating how it should be
downloaded.
Note: When multiple types of data are selected within one content source, the data loading
exercise can be resource intensive.
Note: The best practice would be to split the DPL and HTS/ECCN codes or group data type
subscriptions into multiple content sources and schedule them to run at different times.
Adding a Content Source:
1. Enter an ID in the Content Source ID field.

2. Enter the name of the source in the Source Name field.
3. Select the domain for which this source will be used from the Domain Name drop-down list.
Content Source Data Type
1. Enter a sequence number in the Sequence field. This number determines in which order this
data will be loaded if multiple data types are being downloaded.
2. Enter the data type from the Descartes status document in the Source Data Type field, for
example ECCN. You can find the data type on the Descartes status document.
3. Enter the country ID from the Descartes document in the Source Country ID field.
4. Select the Supported check box if the data type is compatible with your system.
5. Enter the corresponding content type ID in the Content Type field.
6. Click Save .
7. Click Finished . The content source is saved.
Note: You can add as many content source data types as you need.
Configuration
Click New Content Source Config to open the Configuration window.
Related Topics
Content Source Configuration
Download Data Content
GTM Power Data
TRADE M ASTER DATA

Related Topics
This page is accessed via Trade Master Data > Process Management > Trade Master >
Data Load > Download Data Content .
Use this page to download data from a content source. Once the content source is defined, you can
trigger the download process from Download Data Content page.
This process connects to the external system using the URL specified for the external system in the
content source and downloads an XML file known as a status document. The XML file downloaded
from Descartes (or another third party data provider) specifies the current status of the data
available in GTM, the dates when it was last updated, and a link to download new data. It then
parses the status document and downloads any data type available and that is supported by the
Content Source. This process downloads only the new content available.
Note: If you have any issue with the previously downloaded content, select the Force Reload Data
Content check box to download the required content once again.
The Download Data Content process creates a content set record in the database. The Content Set
ID in GTM corresponds to the "Version_ID" field in the Descartes' status document. GTM then
retrieves the zipped files specified as active in the content source. For every data type or zip file
downloaded, GTM adds a record in the Data Load table and an entry in the Content Set Detail
section of the Content Set page. Next, GTM unzips the downloaded files, prepares a CSV file with
the downloaded data and then moves the data into the database using the CSV upload utility.
Finally, GTM sets the status in the Content Set Detail section as Processed.
You can search for a content set using the Content Set ID, on the last content set loaded, or other
criteria. The status fields in the Content Set and the Content Set Detail sections convey whether or
not the processing of the downloaded files was successful.
When you click the Data Load ID link in the Content Set Detail section, you can view information
like the number of records processed (created or updated) by the CSV upload utility. The Number
of Errors field informs you about any failure(s) that might have occurred while processing CSV
records. Errors/failures are also logged during the data load process. If you want to see the log
details related to the data load process, you can turn on the GTM Data load log ID.
If the zip files are downloaded but have not been successfully processed, you can repeat the
process using the Process Downloaded Data action. This may occur when there is a server
shutdown or a network failure.
On the Data Load page, you can see new or updated data version information. GTM uses Data
Version to manage the different versions of data downloaded from the Content Source (i.e.
Descartes or another content provider). Both the product classification codes and restricted party
list (RPL) have a data version associated with them. However unlike RPL, which is delivered
incrementally (after the initial master data file), product classification codes are delivered as
complete sets. Thus, when product classification codes are downloaded, a new data version is
always created and marked as current. With DPL, delta data is appended to the existing data
version.
When a data version is created or updated, a "GtmDataVersionContentUpdated" event is

published, and an agent listening for this event can perform notification.
Whenever a master version of restricted parties is downloaded, the Current flag of the previous
version is marked as ‘N’ (Not Current). This means that all the parties must undergo full screening
against the new data version. After a full screening of your party data against the current list, you
can use the Mark for Purge action to purge the previous data versions and all the restricted parties
which are no longer required.
The following GTM tables are updated by the Download Data Content process for Restricted Party
Lists:
x gtm_content_set
x gtm_content_set_d
x gtm_content_set_d_attr
x gtm_data_load
x gtm_data_load_detail
x gtm_data_load_attribute
x gtm_data_version
x gtm_denied_party
When GTM logs onto the Descartes server, it downloads an XML file that specifies all of the
available data types, the date when they were last updated, an MD5 hash, and a link to download
the file. GTM then determines which files should be downloaded based on what is in the XML file
and what has been defined in the content set.
Note: Integration with Descartes is not done by uploading an XML file. The URL in GTM's external
system points to an XML file on the Descartes server. That XML file is called a status document by
Descartes. The status document is an XML file that specifies the current status of the data
available to GTM, all the available data types, the dates that they were last updated and a link to
download the data files. Based on the information in the status document and how you have
configured GTM (what types to data to download, how often to poll Descartes etc.), GTM will parse
the status document and download any new content available.
This process and the "Process Downloaded Data" process work together and automate the work of
fetching data from a content source and then load this data into a database. The "Download Data
Content" retrieves zip files from the content source. The "Process Downloaded Data" unzips these
files and loads the CSV files into the database.
Note : All downloaded content should be converted to uppercase before downloading.
Note: If you want to download country-specific HS codes, it is recommended that you create all
the necessary data loading configurations in PUBLIC domain only. Also the download process
should be triggered from only the PUBLIC domain. Follow the steps mentioned below in the order
specified:
1. Content Type: Create a new content type within PUBLIC domain with the naming notation: ID >
HTS-<US>. (Replace <US> with any other country that you want to download. This two character
country code should be retrieved from Descartes XML.)
2. Classification Type > HTS <US>. )Replace <US> with any other country that you want to
download. This two character country code should be retrieved from Descartes XML.)
3. Content Source: Create a new content source within PUBLIC domain with any name you like.
You can always refer to the Descartes content source that is shipped with the PUBLIC domain.
4. Link Content Type with Content Source: Edit the new content source that you created and add
records like:
a. Content Source Type - HSN (refer to the PUBLIC shipped content source while entering its
correct value)
b. Source Country ID - US
c. Supported - Yes
d. Content Type - HTS-US (this is the content type create in a previous step)
5. Data Load Type: Create a new data load type within PUBLIC domain with any name you like.
However, make sure that you select the correct content type and content source. For example:
a. Data Load Type - HTS-US_CI
b. Content source - Descartes or any new content source that you created
c. Content Type - HTS-US
Downloading Data Content:
1. Select a content source from the Content Source ID drop-down list.

2. Select the Force Reload Data Content check box.
Note: You can select the Force Reload Data Content check box if you want to download a
fresh copy of a data set, or if you wan to download a new version of a data set. You can also
select this check box to get the correct data set if a download results in errors and a manual
reloading of the data does not resolve the error.
3. Select the Now option to perform the download immediately, or select the Schedule option
to schedule the download for another time.
Note: If you select Schedule , additional fields will open which you can use to set a
scheduled time for the download.
4. Click Submit .
Related Topics
Process Management: Trade Master Data
Content Set
Content Source
Content Type
TRADE M ASTER DATA
Restricted Party List

Parent Restricted Party | Related Topics
This page is accessed via Trade Master Data > Power Data > Restricted Party > Restricted
Party .
Use this page to add new parties to your list of restricted parties.
Once the data content is downloaded from the external content provider and processed
successfully, you will see new or modified restricted party lists under a particular data version. You
can view the details of the restricted parties downloaded in the Restricted Party page. You can also
create your own internal list or red flag list of restricted parties using this page.
Adding a New Restricted Party:

While there are a large number of fields in the Restricted Party page, you are required to enter a
value in only the Data Version ID field. This ID identifies the data subset to which the new
restricted party will be added.
Note : Make sure you always add additional restricted parties such as red flag lists to the data
version that is marked as current and set the restricted party attribute IN_USE = Y. The In Use
option is selected (true) by default. Since the screening process runs on the data version that is
marked as current, this will ensure any restricted parties you add are consider during screening.
Any information you record on this page will generate a screening match if the party being
screened has similar information. For example, if you designate a last name of Frederick and a
state of Texas, any party which matches those criteria will be identified as a restricted party.
Only restricted party records in the Public domain, or the domain you are using will be used for
screening purposes.
Parent Restricted Party

If the new restricted party is associated with another already restricted party (typically in a
parent/child relationship) use this section to add that association.
1. Enter an existing restricted party ID in the Restricted Party ID field.

2. Click Save .
3. Continue adding as many parties as required.
4. When you have no more parties to add, click Finished .
Related Topics
Restricted Party Screening Action
Restricted Party Screening
Restricted Party Exclusion List
GTM Power Data
Restricted Party Screening

Related Topics
This page is accessed via Trade Compliance Management > Power Data > Restricted Party
> Restricted Party Exclusion List.
Use this page to exclude a restricted party from the restricted party screening process. You can
also edit existing exclusions. You can include a party in the Restricted Party Exclusion List which
will enable you to exclude certain parties from the restricted party list, until more information (e.g.,
asking for Letter of Authorization) is collected. The GTM screening process will first check whether
a party is present in the restricted party exclusion list and if it is, GTM will not screen the party
against the denied/restricted party list.
Adding a Restricted Party Exclusion:
1. Enter an ID in the ID field.

2. Fill in as many of the remaining fields as possible.
3. If you are making this exclusion for a limited time, be certain to enter the expiration date in the
Expiration Date field.
4. Select the domain in which this exclusion will apply from the Domain Name drop-down list.
5. Click Finished .
Related Topics
Restricted Party
Restricted Party Screening - Potential Matches
GTM Power Data
GTM Screening Overview
TRADE M ASTER DATA
Purge Data Content

Related Topics
This page is accessed via Trade Master Data > Process Management > Trade Master >
Data Load > Purge Data Content .
Use this page to purge data that is no longer useful once you have downloaded new data content.
Once the data content is downloaded from the external content source and processed successfully,
you can use this page to delete all the downloaded physical files. You can configure your data
content purge process to take place immediately, during the next scheduled process or on a
specific day and time.
Note : This process does not delete the restricted party records you received and are now available
in the Restricted Party List page, but it deletes the files that were downloaded from the content
source.
Purging Data Content
1. Use the Older Than fields to define which data you want to purge.
2. If there were errors during the most recent content upload and you prefer not to purge them
until you have examined them, select the Exclude Data Load With Errors option.
3. Select the Now option to perform the download immediately, or select the Schedule option
to schedule the download for another time.
Note: If you select Schedule , additional fields will open which you can use to set a
scheduled time for the processing.
4. Click Submit .
Related Topics
Process Management: Trade Master Data
TRADE M ASTER DATA
Mark For Purge

Related Topics
This page is accessed via Trade Master Data > Power Data > Data Loading > Data Version
> Mark For Purge.
As an administrator, you can perform a purge based on age of data, status information or domain
name. You can purge downloaded data content (RPL, product classification codes, etc.) using the
standard GTM purge capability available. This process is performed in two steps:
x You can identify and mark the data version to be purged using the Mark For Purge action
available on the Data Version page.
x You can then run the Schedule Purge process which deletes all related data of a particular
data version. The purge process identifies all data versions that are marked for purge and
checks for references. If there are no references, the purge process deletes the data version
and all its data from the child tables. You can configure your data content purge process to
take place immediately, during the next scheduled process or on a specific day and time.
Note : Normally with every new download of the content type of restricted parties, GTM updates the
existing data version. In this scenario, you may not be interested in purging the data version. But if
you want to create a fresh list of restricted parties in a new version, then it is better that purge the
old data version. Generally, the purged data version is more useful with the downloaded content
type of “product classification” since every new download process creates a new data version and
the old data version expires.
Different transaction tables are checked during the purge process of data version related to
Restricted Party and Product Classification.
For Restricted Party related data version purge, the process checks for references in the
GTM_PARTY_SCREENING table.
For Product Classification related data version purge, the process checks for references in the
following tables:
x GTM_ITEM_CLASSIFICATION
x GTM_ITEM_CLASS_TEMPLATE_D
x GTM_REGISTRATION
x GTM_STRUCTURE
x GTM_STRUCTURE_COMPONENT
x GTM_TRANS_LINE_REPORT_QUANTITY
x GTM_TR_ITEM_STRUCTURE
x GTM_TR_PROD_CLASSIFICATION
Related Topics
GTM Power Data
TRADE M ASTER DATA
Screening Service Configuration

Related Topics
GTM offers multiple trade compliance services (e.g., product classification, restricted party
screening, control, license, etc.) to meet different business needs. You can define flexible
configurations to meet different business needs or fine tune each service by using a combination of
the service parameters and service preference entities. GTM ships with a default restricted party
service preference called AD_HOC_PARTY_SCREENING_SERV_PREF. During restricted party
screening, you can use the default preference or create your own service preference.
Related Topics
Restricted Party List Filtering
Match Engine
Exclusion Words
Punctuation List
Match Attributes Selection
Review Match Factor
TRADE M ASTER DATA
Restricted Party List Filtering

Related Topics
This page is accessed via Trade Master Data > Screening Service Configuration > Service
Preference .
In GTM, you can have multiple data versions of the type 'restricted party' that are marked as
current. Each of these data versions represents a restricted party list (e.g. BIS, OFAC, etc.)
specified by the government, a company or a division or red flag words list. You can specify the
restricted party list against which the screening will have to be performed, using the following
service preference attributes:
x Data Source : the content source for the data.

x Data Version : the data version you want to screen against.
x Agency Code : the specific agency that is responsible for the list you are screening.
Note :It is strongly suggested to filter by specifying at least one Data Source and one Data Version
to improve the restricted party screening process.
Related Topics
Service Preference
TRADE M ASTER DATA
Exclusion Words
Related Topics
Preference .
Use this page to maintain a list of exclusion words (e.g., PTE, PVT, GMBH, BLVD, etc.) as part of a
service preference. You should define exclusion words that have no descriptive value or do not
need to be screened. For example, the word ‘company’ is a good choice to be specified as an
exclusion word as it adds no useful information to a party screening. However, words like ‘airline’ or
‘computer’ are not suitable words for exclusion. Restricted party screening service excludes these
listed words from party attributes, if present, before actually performing the screening.
Note : It is strongly recommended that you avoid including a large number of words in the exclusion
list as it could result in a large number of false positives or risk of not identifying valid matches.
Related Topics
Service Preference
TRADE M ASTER DATA
Punctuation List
Related Topics
Preference .
You can maintain a list of punctuation marks (e.g., hyphen "-", question mark "?", exclamation mark
"!", comma ",", semicolon ";" etc.) that should be excluded in the property
gtm.rpsservice.punctuationmarks. The restricted party screening service excludes these marks
from party attributes and restricted party attributes, if they are present, before performing the
screening. It is an application level property that will be applied to all restricted party screening
services.
Related Topics
TRADE M ASTER DATA
Match Attributes Selection

Related Topics
Parameter .
Restricted party screening is all about matching the party with a restricted party list. As part of this
process, one of the important points is to identify the right attributes of the party to be matched with
a restricted party to determine if it is a potential match or not. You can specify the list of attributes
that should be considered during the screening process using the Service Parameter page.
One good and recommended practice is to use direct matching attributes, such as:
x Country attribute of the Party is matched with Country attribute of the Restricted Party
x Province attribute of the Party is matched with Province attribute of the Restricted Party
x City attribute of the Party is matched with City attribute of the Restricted Party
x First Name attribute of the Party is matched with First Name attribute of the Restricted Party
x Last Name attribute of the Party is matched with Last Name attribute of the Restricted Party
x Company Name attribute of the Party is matched with Company Name attribute of the
Restricted Party
This means that when you are creating or modifying party information, you should be sure to enter
the right value in the right field. Add first name in the First Name attribute or add city in the City
attribute instead of entering both these attributes in the Address attribute field.
However, there may be instances where name, city or country information is entered in the Address
attribute field. In such a situation, you can use a parameter such as
“nameCompanyAddressCityProvinceCountry”. This parameter will internally concatenate all the
attribute values of name, company, address, city, province, and country for both the party and the
restricted party and then perform the match.
Note : It is strongly recommended that you use direct matching attributes (e.g. country parameter)
wherever possible and enter the right value in the right field. By using a parameter such as
“nameCompanyAddressCityProvinceCountry”, the quality of the match results might decrease and
could produce a large number of false positives or might not identify valid matches.
Other key points related to parameter selection are match factor and weight, which contribute
towards the overall matching of a party with a restricted party.
For every parameter (match attribute) configured, GTM determines a match factor (matching
percentage) between the party and the restricted party and then compares it against the
corresponding threshold. The threshold field can be used to filter out the restricted parties which
have low match factor for a particular parameter with the result that they are not considered
possible match. You can define a threshold between 0 and 1.
Once GTM determines that a parameter is a match between the party and the restricted party, its
match factor is used along with the weight to calculate the adjusted match factor for that parameter.
After all the parameters are screened and determined to be a match, an overall match factor is
calculated using the adjusted match factor of individual parameters according to the following
formula. The sum of all parameter weights should be equal to 1.
Overall Match Factor = (Match Factor * Weight) of Parameter1
+ (Match Factor * Weight) of Parameter2
+ ………………….+ (Match Factor * Weight) of last Parameter
where, Adjusted Match Factor of parameter1 = (Match Factor * Weight) of Parameter1
Note : It is strongly recommended that you provide a higher threshold (1 or near to 1) for
parameters wherever possible. By default, the restricted party screening process will first match
those parameters that have the highest threshold. If the match threshold fails, GTM stops matching
other parameters immediately and thereby increases restricted party screening performance.
Note : It is strongly recommended that you set the weight of parameters (match attributes) such as
country and/or city as 0. Setting the weight of parameters to 0 means that these specific
parameters (e.g. country or city) will have to pass the individual parameter match factor threshold,
but they would not contribute towards the overall match factor. Another way of looking at it could be
that you want the country and city attributes to match completely, while you want other attributes
like address, company name to contribute more towards the overall match factor.
Related Topics
Service Parameter
TRADE M ASTER DATA
Party Manager Review Match Factor Action

Related Topics
This action is accessed via Trade Master Data > Party Management > Party Manager >
Actions > Screening Services > Review Match Factor .
This page depicts the processing details of matching the party with the restricted party. In the Party
Screening – Potential Matches results page, the upper grid of the page displays all the party details
while the lower grid lists all the potential restricted party matches.
Use the Review Match Factor action available in the Party Manager to determine why a particular
restricted party is not considered as potential match or displayed as part of the restricted party
screening result.
Additional properties that control the behavior of match factor determination are described below.
The default values, which are shown below, are the recommended values.
x gtm.rps.match.useCountryCode=true specifies that the country code will be matched instead

of Country Name.
x gtm.rpls.match.setMatchFactorToZero=true nullifies the contribution of unknown or empty
parameter towards the overall match factor.
x gtm.rpsservice.maxresponse property specifies the maximum number of screening matches
that are returned. The default value for the property is 500.
Use this action to review the results of match outcome for any party against a restricted party. You
need to provide Restricted Party ID and Service Preference ID values.
Reviewing Match Factor:
1. Select a service preference from the Service Preference ID drop-down list.

2. Select Restricted Party .
3. Click Review Match Factor . The Review Match Factor window displays match details for
each field configured in the service parameter.
Related Topics
Party Manager Actions and SmartLinks

Related Topics
Screening is a process whereby each individual or company (business partners) with whom you are
planning to do business is screened against the restricted party list (denied, debarred and/or
restricted parties) to check whether you can conduct business with them. Standard screening is
performed based on first name, last name or company name. Additional optional fields like
alternate name, address, postal code, city, province, and country can be used to determine the
potential matches during screening. Oracle GTM supports transactional and non-transactional
screening of parties.
Related Topics
AD-HOC UI Screening
Screening Service
Party Screening
Transaction Screening
Restricted Party Screening (Ad Hoc)

Screening Criteria | Additional Screening Criteria | Reference Information | Related
Topics
This page is accessed via:
x Trade Compliance Management > Trade Compliance Screening > Restricted Party
Screening
x Ask Oracle > Restricted Party Screening
Ad hoc Restricted Party Screening allows you to screen data of any party without creating a party in
GTM. You can provide all the information of party on this screen. On this screen, information in all
of the fields is compared to restricted party and sanctioned territory information already on file. The
more fields you can complete, the more accurate the screening will be. Any field containing
"unknown" will be ignored. You can also provide a service preference to perform the screening.
Any information you provide in this page will generate a screening match, based on the service
preference used, if there is restricted party with similar information. Once the screening is
completed, the Restricted Party Screening – Potential Matches results page will show the list of
restricted parties matched. For every Restricted Party match, GTM shows the Match Factor,
indicating the percentage of Match. It also highlights the matching characters if ‘Disable
Highlighting’ option is not selected in the Service Parameters page.
Note: To perform both restricted party and sanctioned territory screening from this page, set the
gtm.runSanctionedTerritoryScreenOnParty property to true.
Screening Criteria
Enter a first name, last name, and/or company name into the respective fields.
Note: If you do not designate a service preference, the screening will be run using a default
service preference.
Additional Screening Criteria

Type address information into the respective fields. The address, city, province, and postal code
are all looked at during the screening process.
Reference Information
Use this section if you are screening a specific transaction, a specific source system, or if you
prefer to screen using a specific service preference.
When you have finished entering the information you wish to screen, click Match . The Restricted
Party Screening - Potential Matches window opens with the results of the screening.
Note: If your screening criteria are an exact match to an excluded party, no screening will be
performed. If any party in the results is a complete match to an excluded party, the party will not
appear in the returned results.
Note: The maximum number of matches that are returned is determined by the
gtm.rpsservice.maxresponse property. The property's default value is 500.
Related Topics
Restricted Party
Restricted Party Screening - Potential Matches
GTM Internal Status Designations
GTM Screening Overview
TRADE M ASTER DATA
Screening Service
Related Topics
Restricted Party Screening has been built as a service that can be invoked without the need to
create a party in GTM. You can send a ServiceRequest XML with the input data to the Restricted
Party Screening service, which performs the screening on the input data and returns a
ServiceResponse XML. You can invoke the service request via HTTP post or Web services. Please
refer to the integration guide for more details on the input and output schema/WSDL definition of
this service.
Related Topics
TRADE M ASTER DATA
Party Screening
Related Topics
This page is accessed via Trade Master Data > Party Management > Party Manager .
Any party (individual or company) defined in GTM can be screened against the restricted party list
using the web, agent action or process actions available in the GTM Party Manager. You can
execute multiple screenings (e.g., BIS, OFAC, and Red Flag) with different service preferences on
the same GTM party. The screening process executes the following steps:
1. Screening service gets the party and service preference as inputs.

2. Locks the Party.
3. Retrieves the list of restricted parties based on the service preference and uses attributes like
Data Source, Data Version, Agency Code, etc.
4. For every restricted party, the screening is performed for each service parameter configured
in the Service Parameters page (e.g. first name, last Name, Company Name, Address, City,
Country, etc). Screening of the service parameter with a higher threshold is performed before
screening of the service parameters with a lower threshold in order to reduce the number of
matches.
Note: Party data includes fields labeled Province and Province Code . When restricted
party screening is performed, the Province field is compared to the State or Province field.
If there is no data in the Province field, then the province code data will be screened against
the State or Province field on restricted party data.
Note: To ensure better screening performance, keep the following in mind:

Use Country and/or City as service parameters with a non-zero threshold.
Use Content Source, Agency Code, and or Data Version lists as service preference
parameters.
Use excluded words to reduce the number of unwanted matches.
5. Each service parameter is matched using the match engine specified in the Service
Preference page and a match factor is determined.
x UNKNOWN value on any field or XX value on Country Code field of the Restricted Party
is treated as an empty value.
x If the company name is configured as a parameter, GTM performs the screening using
the company name and calculates the match factor. Then an additional screening is
performed using the alternate name of the party and another match factor is calculated.
The higher of the two match factors is considered as the resultant match factor for the
parameter.
6. If the match factor value is less than the threshold specified in the Service Parameter page,
the restricted party is assumed as not a match and screening against the restricted party is
stopped. If the match factor value is greater than or equal to the threshold, an adjusted match
factor is calculated.
7. An overall match factor is calculated by adding all the adjusted match factors. The restricted
party is considered as match only if the overall match factor is greater than or equal to the
overall threshold specified in the Service Preference page.
8. All the matched restricted parties are saved against the party as a “POTENTIAL MATCH” and
the status of the party is set as “REQUIRES REVIEW”. In case there are no matched
restricted parties, the status of the party is set to “PASSED”.
Note: A status will be assigned when the screening process is completed. For more
information about internal status designations, see GTM Internal Status Designations.
9. Lock on the party is released.
GTM supports the following restricted party screening:
x Web: Use this action to immediately trigger the screening process on a party and
display the potential match results.
x Agent : Use this action to trigger the screening process in the background, based on
events. You can listen/subscribe to events like CONTACT – CREATED, CONTACT –
NAME OR ADDRESS MODIFIED, LOCATION – ADDRESS MODIFIED.
x Process : Use this action to perform mass screening of all parties.
Following is a detailed explanation of the use of the screening options available in GTM for different
business scenarios.
x Scenario-1 : A Restricted Party List is available in GTM and a new GTM party is created. You
can perform restricted party screening on this party using the web action or an agent action.
This is called full screening since you are screening the party against the entire list of
restricted parties.
x Scenario-2 : A Restricted Party List is available in GTM and a GTM party is modified after a
previous screening. You can perform a rescreening against the restricted party list using the
web action or agent action. A full screening will be performed, i.e. screening of modified party
will be performed on the entire list of restricted parties.
x Scenario–3 : A Restricted Party List is available in GTM and all GTM parties are previously
screened. There are no changes to party, service preferences, or restricted party list. You can
perform re-screening of the party against the restricted party list. Since there are no changes
to the details, GTM will not perform any screening. This is also referred to as no screening.
x Scenario–4 : A Restricted Party List is available in GTM and all GTM parties were previously
screened. A user decides to modify the service preference (e.g. updating the exclusion
words, changing the punctuation marks, modifying the screening field parameters, changing
the individual field threshold or overall threshold, etc.). You will need to perform re-screening
of all parties. GTM will perform screening on each party against the entire list of restricted
parties. You can perform this by using the Restricted Party Process page and selecting all the
parties for screening.
Note : When submitting this process request, be sure to select the ‘create new process’
option.
screened. A user downloads the latest restricted party list and there are new or modified
restricted parties on the list. You will need to perform re-screening of all parties against the
restricted party list. GTM will perform screening of each party against the delta list of
restricted parties. This is also referred to as delta screening. You can perform this by using
the Restricted Party Process page and selecting all the parties for screening.
option.
screened. A user downloads the new restricted party list. You will need to perform re-
screening of all parties against this new list. GTM will perform screening of each party against
the entire new list of restricted parties. It is also referred to as full screening. You can perform
this by using the Restricted Party Process page and selecting all the parties for screening.
option.
screened. If you already performed restricted party screening against this list, GTM would not
perform any screening as there is no change in data between the current and the previous
screening. However, if you want to perform a force screening, you can modify the service
preference update_date attribute via backdoor sql. Once this done, you can perform
screening of each party against the entire new list of restricted parties. This is also referred to
as full screening. You can perform this by using the Restricted Party Process page and
selecting all the parties for screening.
Note: When submitting this process request, be sure to select the ‘create new process’
option.
You can turn on the GtmPartyScreen log before screening and identify from the logs whether a full
screening or delta screening was performed. For example, the logs show that the party was last
screened on 2014-03-11 10:41:50 UTC and after that there was no change to the party, service
preference configurations, data version or exclusion list. Hence, full screening was not performed;
but the last change made to some denied parties was on 2014-03-11 10:43:48 UTC and hence, the
delta screening was performed against all those denied parties changed between the 2014-03-11
10:41:50 UTC and 2014-03-11 10:43:48 UTC.
Related Topics
Party Manager
Transaction Screening
Related Topics
In order to ensure you do not ship to a restricted or denied party, you should screen the parties on
your transactions against the restricted party lists.
The screening process executes the following steps on your transaction:
1. Screening service gets the service preference as an input.

2. All the parties on the trade transaction/declaration as well as the corresponding lines are
retrieved.
3. Screening is performed on any party not screened previously. You can avoid screening of any
party on trade transaction/declaration by excluding it using
gtm.rps.involved_party_qual.exclude property. For example, you may want to exclude
screening of all your SHIP_FROM involved parties since all the facilities you ship from are
company owned. Since all the facilities are internal, you can bypass screening for them.
4. Next, the RPLS status of trade transaction/declaration line is set to:
x TL_RPLS_FAILED if there is even one party with the RPLS_FAILED status.
x TL_RPLS_REQUIRES REVIEW if there is no party with the RPLS_FAILED status but at
least one party with RPLS_REQUIRES REVIEW status.
x TL_RPLS_PASSED if none of the parties have the RPLS_REQUIRES REVIEW or
RPLS_FAILED status.
5. Then, the RPLS status of trade transaction/declaration is set to:

x TS_RPLS_FAILED if there is even one trade transaction/declaration line with the
RPLS_FAILED status.
x TS_RPLS_REQUIRES REVIEW if there is no trade transaction/declaration line with the
RPLS_FAILED status but at least one trade transaction/declaration line with
RPLS_REQUIRES REVIEW status.
x TS_RPLS_PASSED if none of the trade transaction/declaration lines have the
RPLS_REQUIRES REVIEW or RPLS_FAILED status.
Note : The shipment execution is stopped for any transaction with an RPLS_FAILED status.
It is recommended to:
x Pre-screen all the parties before using them on a trade transaction/declaration .

x If there is a change in any of the restricted party screening properties, you should trigger
complete rescreening.
x When there are a large number of parties to be screened, you can scale up by increasing the
threads on the ‘agentGtmPartyScreenEventQueue’ Event Group.
x When there are a large number of parties to be screened, you can scale up using the
scalability capability. By using scalability, you can route the restricted party screening request
to a dedicated application instance. Please refer to the Scalability Guide on scalability
configuring.
x You can increase the WebLogic TLA parameter to help when maximum number of threads
are in use and are struggling for resources.
Related Topics
Restricted Party Screening Resolution

Related Topics
Once restricted party screening is performed on the parties, the trade compliance user must
manually verify all potential match results and mark each potential match as valid or invalid. As
there can be a large number of parties and performing review of all potential matches may be time
consuming, GTM provides the concepts of Restricted Party Screening Workbench and Restricted
Party Screening Work Queue to help trade compliance users quickly resolve their potential
matches.
Related Topics
Using the Restricted Party Screening Workbench
Using the Restricted Party Screening Work Queue

Related Topics
This page is accessed via Trade Compliance Management > Trade Compliance Screening
> Restricted Party Screening Workbench .
The Restricted Party Screening Workbench is a highly efficient clearing environment for restricted
party screening potential match resolution. It provides the following capabilities:
x It uses an advanced layout to provide you with a user-friendly interface, showing all the data
you need to make a resolution regarding the potential matches.
x Saved query capability helps you to determine which parties should be available in the
workbench.
x Different buttons, like the Pass, Fail, Escalation, Comments, and Match Factor Review
buttons, are available to help you to quickly take action against all potential matched
restricted parties associated with a party.
To get a detailed description of all the features available in this page, please refer to the topic
Restricted Party Screening Workbench.
Related Topics
GTM Transfers of Information (TOIs)

Related Topics
This page is accessed via Trade Compliance Management > Trade Compliance Screening
> Restricted Party Screening Board - Work Queue .
Restricted Party Screening Work Queue is a highly efficient clearing environment for restricted
party screening potential match resolution. It enables you to define how work is divided into
separate queues for each user to complete. It provides the following capabilities:
x Works in the same way as Restricted Party Screening Workbench, but uses work queues to
pull parties into the advanced layout instead of a saved query.
x Provides a customized distribution of work among various users with separate queues
assigned to each user.
x Provides the ability to reclaim work that has been given to specific users and put it back into
the primary queue.
To get a detailed description of all the features available in this page, please refer to the topic
Restricted Party Screening Board - Work Queue.
Related Topics
TRADE M ASTER DATA
Match Engine Overview

Related Topics
GTM supports six match engines for you select from and specify the algorithm to be used for
restricted party screening. You can select a particular engine to be used in a screening task by
specifying it in the Trade Master Data > Screening Service Configuration > Service
Preference window. Following are the match engines available:
x Exact Match engine checks for a complete match between the party and the restricted party
details.
x Substring Match engine checks whether the party details match with that of the restricted
party and vice-versa.
x Keyword Match checks for the number of restricted party words present for the party.
x Dice engine checks for common bigrams to calculate a dice coefficient, which in turn is used
to calculate the match factor. It is used as the default match engine if no other engine is
selected.
x Soundex and Metaphone engines are phonetic algorithms. These engines encode the
party and the restricted party data and then apply the dice engine on the encoded results to
find possible matches.
Note : The match factor determined using Exact or Substring engine will always be 0 or 1, but for
other match engines it can vary from 0 to 1.
Related Topics
TRADE M ASTER DATA
Exact Match
Related Topics
You can select the engine to be used for screening by specifying it in the Trade Master Data >
Screening Service Configuration > Service Preference window.
This engine identifies exact matches between the party data and the restricted party data. For
example, if you are using this engine for screening, the match factor of matching the word “OSIEL”
against “OSIEL CARDENAS GILLEN” is 0 as it is not an exact match.
Related Topics
Substring Match
Keyword Match
Dice
Soundex
Metaphone
TRADE M ASTER DATA
Substring Match
Related Topics
This engine checks if the party detail is present for the restricted party or the denied party detail is
present for the party. The match factor of matching the word “JORGE” against the words “JORGE
SALINA AGUILAR” or matching the words “JORGE SALINA AGUILAR BIN LADEN” against the
word “JORGE” is 1, as the matching is bidirectional.
Note: This match engine should be used only if the matching takes place both ways.
Related Topics
Exact Match
Keyword Match
Dice
Soundex
Metaphone
TRADE M ASTER DATA
Keyword Match
Related Topics
This engine looks for the number of restricted party words present for the party to determine
the match percentage. It works in only one direction - from restricted party to party. For example,
matching the word “Nuclear” against the words “Nuclear Corporation” results in 0.5% as match
factor, but matching the words “Nuclear Corporation” against the word “Nuclear” results in 1 as
match factor.
Related Topics
Exact Match
Substring Match
Dice
Soundex
Metaphone
TRADE M ASTER DATA
Dice
Related Topics
You can select the engine to be used for screening by specifying it in Trade Master Data >
Screening Service Configuration > Service Preference .
This engine uses the occurrence of bigram characters (two characters) in the party and the
restricted party data to compare and compute a coefficient value, which in turn is used to determine
the match percentage. The output match factor can vary from 0 to 1. Dice can be employed to
compare double-byte characters as well.
Matching Factor Calculation by Dice Engine:
1. Split the party and the restricted party details into words.
2. Since there can be multiple words for the party and the restricted party, GTM prepares all
possible combinations of two words (one from party detail and another from restricted party
detail), computes their bigrams and then checks for their matching percentage using Dice
Coefficient.
GTM calculates the Dice Coefficients between two words (one from the party and other from
the denied party) using the following formula:
Dice Coefficient Formula = [2 * NC/{NC + Maximum(N1 , N2)}]
where,
Number of Bigrams of Party word = N1
Number of Bigrams of Restricted Party word = N2
Number of common Bigrams of Party and Restricted Party word= NC
3. Remove all that are not a match: two words with zero Dice Coefficient is not a match.
4. For every party word, identify the best target word match.
5. Calculate the match factor using the best matches.
Detailed Example of Match Factor Calculation Using Dice Engine:

Let us take an example of a party with the name “SALINA AGUILIAR” and a restricted party with
the name “CARO SALINAS AGUILAR”. Following are the steps showing how the match factor is
calculated.
1. Split the party and the restricted party full name into words.
a. Token(“SALINA AGUILAR”) ={“SALINA”, “AGUILAR”}
b. Token(“CARO SALINAS AGUILIAR”) ={“JORGE”, “SALINAS”, “AGUILIAR”}
2. Prepare a combination of two words (one from the party and the other from the restricted
party). Find their bigrams and calculate Dice Coefficient for every such combination.
Party: Full Name Restricted Party: Full Name Dice Coefficient

“CARO”
Biagrams={“CA”,“AR”,“RO”}
Number of Restricted party Bigrams = 3 2*0/(0+5) = 0
Number of Common Bigrams = 0
Maximum (N1 , N2) = 5
“SALINA” “SALINAS”
Biagrams= Biagrams = {“SA”,“AL”,”LI”,”IN”,”NA”,”AS”}
2*5/(5 + 6) = 10/11
{“SA”,”AL”,“LI”,“IN”,“NA”} Number of Restricted party Bigrams = 6
= 0.909
Number of Source Number of Common Bigrams = 5
Bigrams = 5 Maximum (N1 , N2) = 6
“AGUILIAR”
Biagrams={“AG”,GU”,”UI”,”IL”,”LI”,”IA”,“AR”}
Number of Restricted party Bigrams = 7 2*1/(1+7) = 0.25
“CARO”
Biagrams={“CA”,“AR”,“RO”}
2*1/(1+6) =
Number of Restricted party Bigrams = 3
2/7=0.2857
“AGUILAR” “SALINAS”
Biagrams= Biagrams = {“SA”,“AL”,”LI”,”IN”,”NA”,”AS”}
{“AG”,“GU”,“UI”,“IL”,”LA”, Number of Restricted party Bigrams = 6 2*0/(0 + 6) = 0
“AR”}
Number of Source
Bigrams = 6 Maximum (N1 , N2) = 6
“AGUILIAR”
Biagrams={“AG”,GU”,”UI”,”IL”,”LI”,”IA”,“AR”}
2*5/(5 + 7) = 10/ 12
Number of Restricted party Bigrams = 7
= .0833
3. Remove all non-matches (i.e. with zero Dice Coefficient).
“SALINA” “CARO” 0.00
“AGUILAR” “SALINAS” 0.00
The remaining combinations are:

“SALINA” “SALINAS” 0.909
“SALINA” “AGUILIAR” 0.25
“AGUILAR” “CARO” 0.2857
“AGUILAR” “AGUILIAR” 0.833
4. Identify the best matches among the remaining combinations. Example – the Party Full Name
“SALINA” had two Restricted Party Full Name matches “SALINAS” and “AGUILIAR” with
0.909 and 0.25 respectively, and the best match is “SALINAS” with 0.909 Dice Coefficient.
“SALINA” “SALINAS” 0.909
“AGUILAR” “AGUILIAR” 0.833
5. Calculating the match factor.
Party: Full Restricted Party: Full Dice Number of Matching

Name Name Coefficient Party Characters
“SALINA”
Number of “SALINAS” 0.909 6 * 0.909 = 5.45
Characters =
6
“AGUILAR”
Number of “AGUILIAR” 0.833 7 * 0.833 = 5.831
Characters =
7
Total Number of Characters in Party’s Full Name = 6 + 7 = 13 Total = 11.281
Match Factor of Full Name = Total Number of Matching Characters/Total Number of Characters
M = 11.281/13 = 0.8677 = 87%
Related Topics
Exact Match
Substring Match
Keyword Match
Soundex
Metaphone
TRADE M ASTER DATA
Soundex
Related Topics
This engine uses a phonetic algorithm and fixed-length keys for indexing names by sound, as
pronounced in English. Soundex code for a string consists of a letter followed by three numerical
digits. The letter is the first letter of the name and the digits encode the remaining consonants.
Similar sounding consonants share the same digit. Vowels can affect the coding, but are not coded
themselves except as the first letter. Matching is performed in two steps:
1. Encoding of the party and the restricted party details.

x b, f, p, v => 1
x c, g, j, k, q, s, x, z => 2
x d, t => 3
x l => 4
x m, n => 5
x r => 6
x h, w are not coded
x Two adjacent letters with the same number are coded as a single number.
x Letters with the same number separated by an h or w are also coded as a single
number.
x Continue until you have one letter and three numbers. If you run out of letters, fill in 0s
until there are three numbers.
2. Matching the encoded output using the Dice Engine.
Detailed Example of Matching the Encoded Output:

Let us take an example of a party with the name “MULLAH” and a restricted party with the name
“MAULAVI”. Following are the steps showing how the encoded output is matched.
1. Encoding.
Party: Full Name Restricted Party: Full Name
Encoding(MULLAH)
Encoding(MAULAVI) = M410
= M400
2. Dice engine matching:
a. Bigrams(ML) = {M4, 40, 00}, Bigrams(MLF) = {M4, 41, 10}
b. Common Bigrams = {M4}
c. Dice Coefficient = (2*1)/(1+3) = 0.50
d. Total Number of Letter Matches for Party word (MULLAH) = 0.5 * 6 = 3
e. Match factor of Full Name = Number of Letter Matches/Total Number of Letters on
Party = 3 /6 = 0.5 = 50%
Related Topics
Exact Match
Substring Match
Keyword Match
Dice
Metaphone
TRADE M ASTER DATA
Metaphone
Related Topics
Screening Service Configuration > Service Preference .
This engine uses a phonetic algorithm and variable length keys for indexing names by sound, as
pronounced in English. Matching is performed in two steps:
1. Encoding of the party and the restricted party detail.

If the word begins with 'KN', 'GN', 'PN', 'AE', 'WR', drop the first letter. Eg: KNOWLEDGE
becomes NOWLEDGE.
'PH' transforms to 'F' e.g.: 'PHONE' transforms to 'FONE'.
'Q' transforms to 'K' e.g.: 'QUEEN' transforms to 'KUEEN'.
2. Matching the encoded output using the Dice Engine.
Detailed Example of Matching the Encoded Output:

Let us take an example of a party with the name “MULLAH” and a restricted party with the name
“MAULAVI”. Following are the steps showing how the encoded output is matched.
1. Encoding.
Party: Full Name Restricted Party: Full Name
Encoding(MULLAH) = ML Encoding(MAULAVI) = MLF
2. Dice engine matching:

a. Bigrams(ML) = {ML}, Bigrams(MLF) = {ML, LF}, Common Biagrams = {ML}
b. Dice Coefficient = (2*1)/(1+2) = 0.67
c. Removing non matches and finding out best matches
d. Total Number of Letter Matches for Party word (MULLAH) = 0.67 * 6
e. Match factor of Full Name = Number of Letter Matches/Total Number of Letters on
Party = 0.67 * 6/6 = 0.67 = 67%
Related Topics
Exact Match
Substring Match
Keyword Match
Dice
Soundex

Restrictedpartyscreening

Uploaded by

Copyright:

Available Formats

Restrictedpartyscreening

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Restrictedpartyscreening

Uploaded by

Copyright:

Available Formats

TRADE COMPLIANCE M ANAGEMENT

About Restricted Party Screening

Note : The preferred content provider for GTM is Descartes.

GTM Transfers of Information (TOIs)

Global Trade Content

x Denied Party Screening Lists

Follow the steps below to download your data content:

x Content Source Configuration

GTM Content Source

Adding a Content Source:

1. Enter an ID in the Content Source ID field.

Content Source Data Type

Download Data Content

When a data version is created or updated, a "GtmDataVersionContentUpdated" event is

Downloading Data Content:

1. Select a content source from the Content Source ID drop-down list.

Restricted Party List

Adding a New Restricted Party:

Parent Restricted Party

1. Enter an existing restricted party ID in the Restricted Party ID field.

Restricted Party Exclusion List

Adding a Restricted Party Exclusion:

1. Enter an ID in the ID field.

Purge Data Content

Purging Data Content

Mark For Purge

Screening Service Configuration

Restricted Party List Filtering

x Data Source : the content source for the data.

Match Attributes Selection

Overall Match Factor = (Match Factor * Weight) of Parameter1

+ (Match Factor * Weight) of Parameter2

+ ………………….+ (Match Factor * Weight) of last Parameter

where, Adjusted Match Factor of parameter1 = (Match Factor * Weight) of Parameter1

Party Manager Review Match Factor Action

x gtm.rps.match.useCountryCode=true specifies that the country code will be matched instead

Reviewing Match Factor:

1. Select a service preference from the Service Preference ID drop-down list.

Screening Restricted Parties

Restricted Party Screening (Ad Hoc)

This page is accessed via:

Additional Screening Criteria

1. Screening service gets the party and service preference as inputs.

Note: To ensure better screening performance, keep the following in mind:

9. Lock on the party is released.

GTM supports the following restricted party screening:

The screening process executes the following steps on your transaction:

1. Screening service gets the service preference as an input.

5. Then, the RPLS status of trade transaction/declaration is set to:

x Pre-screen all the parties before using them on a trade transaction/declaration .

Restricted Party Screening Resolution

Using the Restricted Party Screening Workbench

Using the Restricted Party Screening Work Queue

Match Engine Overview

Matching Factor Calculation by Dice Engine:

Dice Coefficient Formula = [2 * NC/{NC + Maximum(N1 , N2)}]

Number of Bigrams of Party word = N1

Number of Bigrams of Restricted Party word = N2

Number of common Bigrams of Party and Restricted Party word= NC