Skip to Content
avatar image
Former Member

InfoObject ZDATE is not a basis characteristic; not used as data target

Hello experts,

I want to load master data hierarchies into an InfoObject from a flat file, thus i want to define this infoobject as an infoprovider

In order to do that i use the "Insert characteristic as InfoProvider" option from the InfoArea but i get a message :

InfoObject  ZDATE is not a basis characteristic; not used as data target

This InfoObject data type is date and has NO attributes assigned to it. Can someone help me to resolve this issue?

Thanks for your help and happy new year.

Best Regards,


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    Dec 25, 2014 at 06:54 AM


    for the ZDATE have you maintained the attr,text,heir if yes it is possible other not possible to convert char to info provider.

    for char object have the possiblility not for the time char.

    can you explain which object you want convert from char to info provider?



    Add comment
    10|10000 characters needed characters exceeded

    • Dear, I think the issue here is your ZDATE infoobject is created based on reference to some other infoobject(0DATE i suppose) .

      For Eg Reference char is ZTEST_M in the below screenshot for the Infoobject ZTEST_R

      Check to which Infoobject your ZDATE refers to and maitain hierarchy for that infoobject .......It will refelect for your ZDATE as well......but before doing all this kindly check the impact of doing the changes.....identify where all it is used by using  where used list option..


      sdn.jpg (103.7 kB)
  • Dec 25, 2014 at 10:04 AM

    Hi Naveen,

    If I understand your situation correctly, you defined a custom Characteristic ZDATE which is referencing Time Characteristic 0DATE. So the Basic Characteristic is in this case 0DATE. Any kind of hierarchies are normally defined on the Basic Characteristic.

    However a Time Characteristic is a special kind of Characteristic and you do not have all options compared to a "normal" (non-time) Characteristic.

    Did you consider using Virtual Time Hierarchies? This might cover your business requirement. Please refer to SAP Help for more information.

    Best regards,


    Add comment
    10|10000 characters needed characters exceeded

    • Hi Naveen,

      Unfortunately I don't have access to an SAP system right now. Did / Can you try to create a Hierarchy on Time Characteristic 0DATE?

      Alternatively, I suggest to add addtional Time Characteristics in the Time Dimension of your InfoCube and use the standard time conversion rules in the Transformation. This is an approach which I normally use and which works very well, also from a performance point-of-view.

      Best regards,