7.5.1 Tables Required for GTO

(In order to correctly generate scenario which consider the GTO threshold set, you must provide data which populates the following tables:

Note:

KDD_CTR_DEDUP_PREF: This table defines which CTRs should be treated as group based on which scenario threshold set created the CTR. This is used to establish the Shared Transaction Among CTR functionality. It is mandatory to provide the thresholds being used

Table 7-1 Fields in KDD_CTR_DEDUP_PREF

Fields	Descriptions
N_DEDUP_PREF_SKEY	Uniqueidentifier to identify the groups created for performing de-duplication.
TSHLD_SET_ID	Thresholdset ID for the thresholds being used. Can be obtained from the KDD_TSHLD_SET table using the Scenario ID as a filter.
TSHLD_SET_NM	Thresholdset name for the thresholds being used. This can be obtained from the KDD_TSHLD_SET table using the Scenario ID as a filter.
N_GROUP_ID	Determinesthe group for performing de-duplication. CTRs belonging to the same group will be considered for auto-closure according to the de-duplication logic.

Note:

There must be no leading or trailing spaces while populating data in these tables

KDD_CTR_EXCLUSION: This table records which account IDs or TINs should be excluded when executing GTO scenarios.

Table 7-2 Fields in KDD_CTR_EXCLUSION

Fields	Description
N_XCLSN_SKEY	Uniqueidentifier to identify the exclusion.
V_XCLSN_ID	IDfor the exclusion list. Note:Thislist of exclusion IDs is passed as the threshold set parameter value for the Exclusion List ID threshold.
V_XCLSN_DESC	Descriptionof the exclusion list.
V_XCLSN_TYPE	Distinguishesbetween account-based and TIN-based exclusion lists. Possible values are ACCT and TIN
V_XCLSN_VALUE	Thevalues of entities to exclude. IfV_XCLSN_TYPE = ACCT then the acct_intrl id will be provided. For example: BAST124 If V_XCLSN_TYPE = TIN the value should be in the concatenatedformat (taxid format type||'~'|| tax_id ) For example: - S~123123123
D_DEACT_TS	Deactivationor expiration date for the exclusion list.

• For Customer-focused scenarios - Only account-based exclusions will be considered.
• For Conductor-focused scenarios - Both account and TIN-based exemptions will be considered, however the TIN-based exclusion will be limited to the conductor’s tax ID.
• For TIN-focused scenarios - Both account and TIN-based exemptions will be considered. TIN- based exclusions will be run on both customer and conductor TINs

For more information on tables used to populate data for CTR, see the Data Interface Specification and FSDM Reference Guide Vol. 1: Business Data.