Create a Sanctioned Screening

post

/tradeParties/{contactGid}/sanctionedScreenings

Request

Path Parameters
Supported Media Types
Request Body - application/vnd.oracle.resource+json;type=collection ()
Root Schema : schema
Type: object
Show Source
Nested Schema : items
Type: array
Show Source
Nested Schema : schema
Type: object
Show Source
  • The GID for the GTM compliance rule. You can configure screening to fit any combination of rules or policies that you deem to be necessary. Compliance rules can be added to a rule set, rule sets can be added to rule set groups, and rule set groups can be combined into a compliance policy which is then used in transaction screening.
  • The GID for the GTM compliance rule group. The compliance rule group is considered an optional input for sanctioned territory screening. If no compliance rule group is provided, the service preference given in user preference is considered for getting compliance rule group information. If a user preference has not been designated, screening will be done against all sanction rules using the Cumulative algorithm.
  • The control type and control code are linked to the compliance rule.
  • The GID for the GTM control type. The control type is linked to the compliance rule.
  • Database domain where this data is stored.
  • The GID for the GTM sanctioned territory screening. If sanctioned territory screening has taken place via either Trade Compliance Screening or the Sanctioned Territory Screening action, the results will be stored here.
  • The XID for the GTM sanctioned territory screening. If sanctioned territory screening has taken place via either Trade Compliance Screening or the Sanctioned Territory Screening action, the results will be stored here.
  • links
    Read Only: true
  • The GID for the GTM regulation reference. The regulation reference is related directly to a compliance rule.
Nested Schema : links
Type: array
Read Only: true
Show Source
Request Body - application/vnd.oracle.resource+json;type=singular ()
Root Schema : schema
Type: object
Show Source
  • The GID for the GTM compliance rule. You can configure screening to fit any combination of rules or policies that you deem to be necessary. Compliance rules can be added to a rule set, rule sets can be added to rule set groups, and rule set groups can be combined into a compliance policy which is then used in transaction screening.
  • The GID for the GTM compliance rule group. The compliance rule group is considered an optional input for sanctioned territory screening. If no compliance rule group is provided, the service preference given in user preference is considered for getting compliance rule group information. If a user preference has not been designated, screening will be done against all sanction rules using the Cumulative algorithm.
  • The control type and control code are linked to the compliance rule.
  • The GID for the GTM control type. The control type is linked to the compliance rule.
  • Database domain where this data is stored.
  • The GID for the GTM sanctioned territory screening. If sanctioned territory screening has taken place via either Trade Compliance Screening or the Sanctioned Territory Screening action, the results will be stored here.
  • The XID for the GTM sanctioned territory screening. If sanctioned territory screening has taken place via either Trade Compliance Screening or the Sanctioned Territory Screening action, the results will be stored here.
  • links
    Read Only: true
  • The GID for the GTM regulation reference. The regulation reference is related directly to a compliance rule.
Nested Schema : links
Type: array
Read Only: true
Show Source
Back to Top

Response

Supported Media Types

Default Response

Default Response.
Body ()
Root Schema : schema
Type: object
Show Source
  • The GID for the GTM compliance rule. You can configure screening to fit any combination of rules or policies that you deem to be necessary. Compliance rules can be added to a rule set, rule sets can be added to rule set groups, and rule set groups can be combined into a compliance policy which is then used in transaction screening.
  • The GID for the GTM compliance rule group. The compliance rule group is considered an optional input for sanctioned territory screening. If no compliance rule group is provided, the service preference given in user preference is considered for getting compliance rule group information. If a user preference has not been designated, screening will be done against all sanction rules using the Cumulative algorithm.
  • The control type and control code are linked to the compliance rule.
  • The GID for the GTM control type. The control type is linked to the compliance rule.
  • Database domain where this data is stored.
  • The GID for the GTM sanctioned territory screening. If sanctioned territory screening has taken place via either Trade Compliance Screening or the Sanctioned Territory Screening action, the results will be stored here.
  • The XID for the GTM sanctioned territory screening. If sanctioned territory screening has taken place via either Trade Compliance Screening or the Sanctioned Territory Screening action, the results will be stored here.
  • links
    Read Only: true
  • The GID for the GTM regulation reference. The regulation reference is related directly to a compliance rule.
Nested Schema : links
Type: array
Read Only: true
Show Source
Back to Top