Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Date LOVs prior to 1970

It appears that date values prior to 1970 are not supported in prompt LOVs.

To test this, I created a universe (unv) with a object having a date value of 5/1/1970 through 5/1/2020.  I then created a report with a prompt on this object.  When I attempt to refresh the report in REST, I get the following response:

<lov searchable="true" refreshable="true" partial="false" hierarchical="false">

<id>UNIVERSELOV_DS0.DO4</id>

<updated>2014-12-29T09:47:38.000-05:00</updated>

<intervals>

<interval id="0">

<value/>

<value/>

</interval>

<interval id="1">

<value/>

<value>2001-04-30T20:00:00.000-04:00</value>

</interval>

<interval id="2">

<value>2002-04-30T20:00:00.000-04:00</value>

<value>2020-04-30T20:00:00.000-04:00</value>

</interval>

</intervals>

<values>

<value/>

<value/>

<value/>

<value/>

All of the "<value/>" rows represent a date prior to 1970.  Note that this is occurring in interval ranges as well as values.  When I request all the values in a single interval, the problem becomes more apparent:

<parameters>

    <parameter dpId="DP0" type="prompt" optional="false">

        <id>0</id>

        <technicalName>Enter value(s) for THEDATE</technicalName>

        <name>Enter value(s) for THEDATE</name>

        <answer type="DateTime" constrained="false">

            <info cardinality="Multiple">

                <lov searchable="true" refreshable="true" partial="false" hierarchical="false">

                    <id>UNIVERSELOV_DS0.DO4</id>

                    <updated>2014-12-29T09:48:20.000-05:00</updated>

                    <values>

                        <value/>

                        <value/>

                        <value/>

                       (multiple identical rows removed)

                        <value/>

                        <value/>

                        <value/>

                        <value/>

                        <value/>

                        <value>1970-04-30T20:00:00.000-04:00</value>

                        <value>1971-04-30T20:00:00.000-04:00</value>

                        <value>1972-04-30T20:00:00.000-04:00</value>

                        <value>1973-04-30T20:00:00.000-04:00</value>

                        <value>1974-04-30T20:00:00.000-04:00</value>

                        <value>1975-04-30T20:00:00.000-04:00</value>

                        (years 1976-2015 removed)

                        <value>2016-04-30T20:00:00.000-04:00</value>

                        <value>2017-04-30T20:00:00.000-04:00</value>

                        <value>2018-04-30T20:00:00.000-04:00</value>

                        <value>2019-04-30T20:00:00.000-04:00</value>

                        <value>2020-04-30T20:00:00.000-04:00</value>

                    </values>

                    <columns mappingId="0">

                        <column type="DateTime" id="0">THEDATE </column>

                    </columns>

                </lov>

            </info>

        </answer>

    </parameter>

</parameters>

Is this a bug, or intentional behavior?

Tags:
replied

The fix will be delivered in 4.1 SP6 :-)

Regards,

eric

0 View this answer in context

Helpful Answer

by
Not what you were looking for? View more on this topic or Ask a question