Bookshelf Home | Contents | Index | Search | PDF     

Siebel Analytics Applications Installation and Administration Guide > Localizing Siebel Analytics Deployments > Process of Maintaining Translation Tables for Analytics >

Importing Siebel Financial Services Metadata Files

This topic is part of the Process of Maintaining Translation Tables for Analytics.

There are differences in the metadata terminology between the Siebel Financial Services application and the metadata terminology of other Siebel operational applications. Siebel Financial Services customers running an implementation in ENU (English) must import the seed data as described in Importing Locale Seed Data into the Siebel Transactional Database.

The files used in the importing of Siebel operational application metadata and seed data are shown in Table 68.

Table 68. Files for Importing Siebel Operational Application Metadata and Seed Data
File Name
Purpose of File

Metadata_upgrade_<XXX>_ora.inp

Metadata_upgrade_<XXX>_mssql.inp

Metadata_upgrade_<XXX>_db2.inp

Set of import files used to control the import of the analytics_seed_<XXX>.dat file to a particular database platform.

XXX is the Siebel Systems three-letter code. For example: FRA, ITA, DEU.

analytics_seed_<XXX>.dat

Set of Siebel seed data files containing translations for all the Siebel Analytics metadata objects. Each file contains all the translations for a single language. These files place translation-related seed data into the S_MSG table in the Siebel transactional database.

XXX is the Siebel Systems three-letter code. For example: FRA, ITA, DEU.
    
Siebel Analytics Applications Installation and Administration Guide