Multi-locale Architecture

18 Multi-locale Architecture

This section lists the tables for Multi-locale Architecture.

Introducing following tables for supporting Multi-locale architecture:

KDD_CASE_TYPE_SUBTYPE_TL
KDD_ACTION_TL
KDD_ACTION_CAT_CD_TL
KDD_CMMNT _TL
KDD_STATUS_TL
KDD_CODE_SET_TRNLN_TL
KDD_LINK_ANLYS_DISPLALY_INFO_TL
KDD_QUEUE_MASTER _TL
KDD_REG_REPORT_STATUS_TL
FCC_EVENT_TYPE_TL
KDD_INSTALL_PARAM_TL
KDD_CASEATTRBT_MASTER_TL
KDD_CASEENTITY_MASTER_TL
KDD_JRSDCN_TL
KDD_BUS_DMN_TL
KDD_ORG_TL
KDD_COUNTRY_TL
FCC_SCENARIO_MASTER_TL
FCC_TPG_SETUP_PARAMS_SRVCS_TL

There may be 2 scenarios:-OPTIONAL STEP ONLY IF below scenario is satisfied:

If any client has applied LP in earlier versions then the base tables will be holding translated strings.

If client has customized few OOB Strings or added new entries to Base tables.

Note:

Client can make use of the attached MergeScript_TL_LP_Customizations.sql. Client need to replace the placeholder ##LOCALE_CD## with their respective locale and execute in Atomic Schema and commit.