7.19 Configuring FSDF

This section describes the configurations for Financial Services Data Foundation (FSDF).

Note:

Release 8.1.2.0.0 uses the BD-AM slice of Oracle FSDF 8.1.2.1.0.

Configuring CSA Staging Tables

If BD and CSA tables are in same schema, run the following SQL file in Atomic schema available in the path <download_dir>/OFS_BD_ PACK/OFS_AML:

FSDFAlterTimezone.sql.

Configuring FSDF in Different Infodom (Pack on Pack Installation)

Upgrade installation from BD 8.1.X.X.X to BD 8.1.2.0.0

If BD and FSDF/OIDF are in different Infodoms, follow these steps:

  1. Run the upgrade installer with FSDF_UPLOAD_MODEL= 0 in PatchConfig.xml OFS_BD_PACK/OFS_AML/conf
  2. Execute the following SQL files in FSDF Atomic schema, available in the path /OFS_BD_PACK/ OFS_AML.

    FSDFAlterTimezone.sql

    Note:

    Drop all the staging tables in the BD atomic schema using the below SQL files

    drop_script - BD FSDF 81210 Staging Tables - FCCM 812 Release.sql

    drop_script - BD OIDF 81210 Staging Tables - FCCM 812 Release.sql

    SeeSTG tablesfor list of staging tables of BD-AM slice of Oracle FSDF 8.1.2.1.0.

  3. Run the following script in BD Atomic schema, after replacing placeholder ##FSDF_ USER## with FSDF Atomic user name in - INGESTUSERSYNONYMFORFSDFSTGSCHEMAOWNER.sql.
  4. Run the following script in FSDF Atomic schema, after replacing placeholder ##FCCM_ USER## with BD Atomic user name in - FsdfStgSchemaOwnergrant.sql.

If BD and FSDF are in different Infodoms and client does not have different OIDF infodom, follow these steps:

  1. Run the upgrade installer with FSDF_UPLOAD_MODEL= 0 in PatchConfig.xml OFS_BD_PACK/OFS_AML/conf
  2. Execute the following SQL files in FSDF Atomic schema, available in the path /OFS_BD_PACK/ OFS_AML.

    FSDFAlterTimezone.sql

    Note:

    Drop only FSDF staging tables in the BD atomic schema using the below SQL file attached

    drop_script - BD FSDF 81210 Staging Tables - FCCM 812 Release.sql

  3. Run the following script in BD Atomic schema, after replacing placeholder ##FSDF_ USER## with FSDF Atomic user name in - INGESTUSERSYNONYMFORFSDFSTGSCHEMAOWNER.sql.

    Note:

    Ignore the ORA errors for the OIDF tables:

    (STG_INS_POLICY_FEATURE_MAP, STG_LIFE_INS_CONTRACTS, STG_LIFE_INS_POLICY_TXNS, STG_PARTY_INS_POLICY_ROLE_MAP,

    STG_INS_SELLER_LICENSE)

  4. Run the following script in FSDF Atomic schema, after replacing placeholder ##FCCM_ USER## with BD Atomic user name in - FsdfStgSchemaOwnergrant.sql.

    Note:

    Ignore the ORA errors for the OIDF tables: STG_INS_POLICY_FEATURE_MAP, STG_LIFE_INS_CONTRACTS,

    STG_LIFE_INS_POLICY_TXNS,

    STG_PARTY_INS_POLICY_ROLE_MAP,

    STG_INS_SELLER_LICENSE)

Standalone OFSBD 8.1.2.0.0 Installation

If BD and FSDF/OIDF are in different Infodoms, follow these steps:

  1. Run the BD812 installer with FSDF_UPLOAD_MODEL= 0 in default.properties OFS_BD_PACK/OFS_AML/conf/default.properties.
  2. Execute the following SQL files in FSDF Atomic schema, available in the path /OFS_BD_PACK/ OFS_AML.

    FSDFAlterTimezone.sql

    Note:

    Dropping the staging tables is not required.
  3. Run the following script in BD Atomic schema, after replacing placeholder ##FSDF_ USER## with FSDF Atomic user name in - INGESTUSERSYNONYMFORFSDFSTGSCHEMAOWNER.sql.
  4. Run the following script in FSDF Atomic schema, after replacing placeholder ##FCCM_ USER## with BD Atomic user name in - FsdfStgSchemaOwnergrant.sql.

If BD and FSDF are in different Infodoms and client doesn’t have different OIDF infodom, follow these steps:

  1. Run the BD812 installer with FSDF_UPLOAD_MODEL= 1 in default.properties OFS_BD_PACK/OFS_AML/conf/default.properties
  2. Execute the following SQL files in FSDF Atomic schema, available in the path /OFS_BD_PACK/ OFS_AML.

    FSDFAlterTimezone.sql

    Note:

    Drop only FSDF staging tables in the BD atomic schema using the below SQL file attached.

    drop_script - BD FSDF 81210 Staging Tables - FCCM 812 Release.sql

  3. Run the following script in BD Atomic schema, after replacing placeholder ##FSDF_ USER## with FSDF Atomic user name in - INGESTUSERSYNONYMFORFSDFSTGSCHEMAOWNER.sql.

    Note:

    Ignore the ORA errors for the OIDF tables:

    (STG_INS_POLICY_FEATURE_MAP, STG_LIFE_INS_CONTRACTS, STG_LIFE_INS_POLICY_TXNS, STG_PARTY_INS_POLICY_ROLE_MAP,

    STG_INS_SELLER_LICENSE)

  4. Run the following script in FSDF Atomic schema, after replacing placeholder ##FCCM_ USER## with BD Atomic user name in the below SQL:

    FsdfStgSchemaOwnergrant.sql

    Note:

    Ignore the ORA errors for the OIDF tables:

    (STG_INS_POLICY_FEATURE_MAP, STG_LIFE_INS_CONTRACTS, STG_LIFE_INS_POLICY_TXNS, STG_PARTY_INS_POLICY_ROLE_MAP, STG_INS_SELLER_LICENSE)

    In case on pack on pack installation, the FSI_PARTY_RIGHT_TO_FORGET table must be manually created. To do this, run the following code:

    create table FSI_PARTY_RIGHT_TO_FORGET (
FIC_MIS_DATEDATE not null,
V_PARTY_IDVARCHAR2(20 CHAR) not null, V_PARTY_FORGET_REASON VARCHAR2(100 CHAR)
not null
);