For some mapping tables, the installation media for SAS^® Credit Risk Management for Banking 4.5 has VALID_TO_DTTM values of 1JAN09. If this date is not modified, then during installation after 1JAN09, these mapping tables will not be copied to the installation datamart. As a result, some of the user formats are not created and the post-installation batch program, installation_batch_job.sas, will fail and generate an error like the following:

• Map_counterparty_relation_type
• Map_equity_position_type
• Map_exchange_type
• Map_position_type
• Map_seniority

To avoid this error within an existing installation, change the date value of VALID_TO_DTTM to an acceptable future date value (for example, by changing the year to 2999), and then run u00_update_group_datamart.sas to move the new mapping tables into the entity data marts.

Details

By default, these mapping tables are initially located on the Server Tier in a directory like the following:

<credit-risk-install-dir>\datamart\mapping

For example:

C:\Program Files\SAS\SASCreditRiskManagement\4.5\datamart\mapping

<credit-risk-install-dir>\sascode\programs

When changing the date value for the VALID_TO_DTTM variable, you can ensure that it is set to the desired year (for example, 2999 instead of 1999) by viewing the year value in a four-digit format. The following SAS code provides an example for viewing the VALID_TO_DTTM year values:

libname temp "<insert-path-to-mapping-tables-here>";
data _null_;
   set temp.map_seniority;
   year = year(datepart(VALID_TO_DTTM));
   put year=;
run;

References

For more information about the VALID_TO_DTTM variable, see the SAS Detail Data Store for Banking 2.5: Implementation and Administration Guide.

For installation details, see SAS Credit Risk Management for Banking 4.5: Installation Guide.

Operating System and Release Information