Forum Stats

  • 3,750,275 Users
  • 2,250,151 Discussions
  • 7,866,890 Comments

Discussions

Import Error || FDMEE

Rabi P
Rabi P Member Posts: 32
edited Oct 18, 2017 2:48AM in Financial Data Management

Hi All,

I am trying to import file with 33 columns. While importing I am getting this below error where it says on

FATAL [AIF]: Error in CommMap.updateTDATASEG_T_TDATASEGW

Traceback (most recent call last):

  File "<string>", line 1712, in updateTDATASEG_T_TDATASEGW

TypeError: len() of unsized object

It seems something with the length of record.

I checked the file but there is nothing abnormal with it. Can someone please help?

Tagged:

Best Answer

  • Rabi P
    Rabi P Member Posts: 32
    edited Oct 18, 2017 2:48AM Accepted Answer

    Hi,

    The issue was in 11.1.2.3.500 On-Premise. There is no issue with the environment.

    The issue was with a multidimensional mapping condition which was not getting processed due to wild characters in the target member. The derivation of  target member was getting processed through logic accounts and then referring to another dimension in Multi-dimensional mapping.

    We used format masking to address the issue.

    Thanks,

    Rabi

Answers

  • USER1211
    USER1211 Member Posts: 3,104
    edited Oct 17, 2017 10:45AM

    is this cloud?

    If on premise What version of  Hyperion(including patch level)?(e.g FDMEE 11.1.2.4.210,Essbase 11.1.2.4.019)

    how many characters is in the field?

    Is this a new environment?

    Have you ever successfully loaded on the environment?

    Have you sough to remove unnecessary columns from the file and only import the few columns you need and see if it works?

    Provide a sample of how the file looks so members can give there input.

  • Rabi P
    Rabi P Member Posts: 32
    edited Oct 18, 2017 2:48AM Accepted Answer

    Hi,

    The issue was in 11.1.2.3.500 On-Premise. There is no issue with the environment.

    The issue was with a multidimensional mapping condition which was not getting processed due to wild characters in the target member. The derivation of  target member was getting processed through logic accounts and then referring to another dimension in Multi-dimensional mapping.

    We used format masking to address the issue.

    Thanks,

    Rabi

This discussion has been closed.