PM56672: TM1 9.5.2 PACKAGE CONNECTOR CANNOT IMPORT NUMERICAL ATTRIBUTES WHEN THE COMMA "," IS USED AS DECIMAL SEPARATOR

APAR status

• Closed as fixed if next.

Error description

• The customer is using the TM1 Package Connector 9.5.2 for BI
  10.1.0 Windows, Version 10.1.4707.511  The server machine
  running the TM1 server software and the TM1 Package Connector
  software is using a dutch Windows, thus the default decimal
  separator is the comma "," and the default thousand separator is
  the dot ".".   The TM1 Package Connector has two basic import
  operations: Importing a cube and importing a single dimension,
  see the manual TM1 9.5.2 Turbo Integrator Guide ->
  http://publib.boulder.ibm.com/infocenter/ctm1/v9r5m0/topic/com.i
  bm.swg.im.cognos.tm1_turb.9.5.2.doc/tm1_turb_id4702ImportingaSin
  gleDimension.html#id4702ImportingaSingleDimension
  TM1 Turbo Integrator Guide 9.5.2 Importing Data Using the IBM
  Cognos TM1 Package Connector > Establishing a Connection to the
  Cognos BI Server > Importing a Single Dimension    Using the TM1
  Package Connector the customer created a TI process to import a
  single dimension and it's numeric attributes.   That TI process
  failed with the error message  ERROR = cannot convert field
  number <nnn>, value <0,00> to a real number.        because the
  numbers of the numeric attributes are using the comma "," as
  decimal separator but the TM1 Package Connector seems to be
  hardcoded to accept only the dot "." as decimal separator.   On
  the same server machine, in the same environment, that problem
  does not happen when the customer is using the TM1 Package
  Connector to create a TI process to import a cube, and the
  numbers to be imported are using the comma "," as decimal
  separator.  Thus the customer compared the TI processes created
  by the TM1 Package Connector importing a cube or importing a
  single dimension: In the generated code of the prolog of the TI
  process to import a cube they found the two Local TI Variables
  "DataSourceASCIIDecimalSeparator" and
  "DataSourceASCIIThousandSeparator" which set the proper decimal
  separator. It looks like the value of the proper decimal
  separator was taken from the Windows Regional Settings of the
  server machine running the TM1 Package Connector software. These
  two lines were missing in the prolog of the generated TI code
  created by the import a single dimension operation.  As the
  import a cube operation automatically takes care of the
  environment specific decimal separator, but the import a single
  dimension does not, the customer is asking to fix the broken
  import a single dimension operation so that it works like the
  import a cube operation:  It shall automatically add generated
  code to the prolog of the TI to take care of the environment
  specific decimal separator.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All Users                                                    *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See error description.                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to IBM Cognos Business Intelligence 10.2 Refresh     *
  * Pack 1                                                       *
  ****************************************************************
  

Problem conclusion

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

• RA11 PSN

     UP