Unparseable date

[Former Member]

Hey guys,

I need some help out here. I'm scheduling a document using RESTful Web Service and it's working so far, but it doesn´t work when I provide a date-time optional parameter. Under this circumstance the webi document is scheduled but the scheduling fails and the mesage reported is "unparseable date".

I've tried dozen formats like 31/12/2015 00:00:00, 12/31/2015, 12/31/2015 00:00:00 AM, datetime'2015-12-31T00:00:01', 2015-12-31T00:00:01, but none of them worked.

Can anyone help me? Is there any reference document for this? I already have the sbo41sp5_bip_rest_ws_en.pdf document, but it doens´t have any reference for this kind of issue.

The post body content is:

<schedule>
  <name>297Mensal</name>
  <format type="webi"/>
  <destination><inbox/></destination>
  <parameters>
  <parameter optional="true" type="prompt" dpId="DP16">
  <id>0</id>
  <technicalName>Vara do Trabalho</technicalName>
  <name>Vara do Trabalho</name>
  <answer>
  <values><value>10ª VARA DO TRABALHO DE GOIÂNIA</value></values>
  </answer>
  </parameter>
  <parameter optional="false" type="prompt" dpId="DP16">
  <id>1</id>
  <technicalName>Rito</technicalName>
  <name>Rito</name>
  <answer>
  <values>
  <value id="0">SUMARÍSSIMO</value>
  </values>
  </answer>
  </parameter>
  <parameter optional="true" type="prompt" dpId="DP17">
  <id>2</id>
  <technicalName>Data inicial:</technicalName>
  <name>Data inicial:</name>
  <answer>
  <values>
  <value>'1/1/2015 00:00:00'</value>
  </values>
  </answer>
  </parameter>
  <parameter optional="true" type="prompt" dpId="DP17">
  <id>3</id>
  <technicalName>Data final:</technicalName>
  <name>Data final:</name>
  <answer>
  <values>
  <value>'31/1/2015 00:00:00'</value>
  </values>
  </answer>
  </parameter>
  </parameters>
</schedule>

I'm using SAP BO 4.1 SP8.

Regards

[Former Member]

Hey Daniel and Anthony,

Thanks a lot for the your response on time. But the problem isn't solve. I've tried from both solutions and none of them worked. Check at the error message, the date format I've input:

• Unparseable date: "2000-01-12T12:13:14Z"
• Unparseable date: "20/1/2015T00:00:00-03:00"
• Unparseable date: "'20/1/2015T00:00:00Z'"
• Unparseable date: "20/1/2015T00:00:00Z"
• Unparseable date: "'1/1/2015 00:00:00'"

Would some CMC or preference setting (language, for instance) be this issue root cause?

When I request the document parameters, that's the Response I get:

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<parameters>
    <parameter optional="true" type="prompt" dpId="DP16">
        <id>0</id>
        <technicalName>Vara do Trabalho</technicalName>
        <name>Vara do Trabalho</name>
        <answer constrained="true" type="Text">
            <info cardinality="Single" keepLastValues="true">
                <lov hierarchical="false" partial="false" refreshable="true" searchable="true" mandatorySearch="false">
                    <id>UNIVERSELOV_DS3.DO7</id>
                    <updated>2016-09-21T13:43:31.000-03:00</updated>
                    <values>
                        <value>18ª VARA DO TRABALHO DE GOIÂNIA</value>
                        <value>VARA DO TRABALHO DE URUAÇU</value>
                        <value>2ª VARA DO TRABALHO DE ITUMBIARA</value>
                        <value>POSTO AVANÇADO DE IPORÁ</value>
                        <value>14ª VARA DO TRABALHO DE GOIÂNIA</value>
                        <value>3ª VARA DO TRABALHO DE GOIÂNIA</value>
                        <value>VARA DO TRABALHO DE INHUMAS</value>
                        <value>VARA DO TRABALHO DE LUZIÂNIA</value>
                        <value>7ª VARA DO TRABALHO DE GOIÂNIA</value>
                        <value>VARA DO TRABALHO DE CALDAS NOVAS</value>
                        <value>13ª VARA DO TRABALHO DE GOIÂNIA</value>
                        <value>1ª VARA DO TRABALHO DE ANÁPOLIS</value>
                        <value>VARA DO TRABALHO DE CATALÃO</value>
                        <value>VARA DO TRABALHO DE CERES</value>
                        <value>VARA DO TRABALHO DE QUIRINÓPOLIS</value>
                        <value>1ª VARA DO TRABALHO DE GOIÂNIA</value>
                        <value>10ª VARA DO TRABALHO DE GOIÂNIA</value>
                        <value>POSTO AVANÇADO DE PORANGATU</value>
                        <value>VARA DO TRABALHO DE GOIÁS</value>
                        <value>6ª VARA DO TRABALHO DE GOIÂNIA</value>
                        <value>4ª VARA DO TRABALHO DE GOIÂNIA</value>
                        <value>2ª VARA DO TRABALHO DE GOIÂNIA</value>
                        <value>1ª VARA DO TRABALHO DE APARECIDA DE GOIÂNIA</value>
                        <value>VARA DO TRABALHO DE FORMOSA</value>
                        <value>VARA DO TRABALHO DE VALPARAÍSO DE GOIÁS</value>
                        <value>3ª VARA DO TRABALHO DE RIO VERDE</value>
                        <value>12ª VARA DO TRABALHO DE GOIÂNIA</value>
                        <value>4ª VARA DO TRABALHO DE RIO VERDE</value>
                        <value>2ª VARA DO TRABALHO DE APARECIDA DE GOIÂNIA</value>
                        <value>3ª VARA DO TRABALHO DE APARECIDA DE GOIÂNIA</value>
                        <value>VARA DO TRABALHO DE SÃO LUIS DE MONTES BELOS</value>
                        <value>16ª VARA DO TRABALHO DE GOIÂNIA</value>
                        <value>17ª VARA DO TRABALHO DE GOIÂNIA</value>
                        <value>8ª VARA DO TRABALHO DE GOIÂNIA</value>
                        <value>1ª VARA DO TRABALHO DE RIO VERDE</value>
                        <value>VARA DO TRABALHO DE MINEIROS</value>
                        <value>1ª VARA DO TRABALHO DE ITUMBIARA</value>
                        <value>VARA DO TRABALHO DE GOIANÉSIA</value>
                        <value>4ª VARA DO TRABALHO DE ANÁPOLIS</value>
                        <value>VARA DO TRABALHO DE POSSE</value>
                        <value>9ª VARA DO TRABALHO DE GOIÂNIA</value>
                        <value>15ª VARA DO TRABALHO DE GOIÂNIA</value>
                        <value>VARA DO TRABALHO DE GOIATUBA</value>
                        <value>5ª VARA DO TRABALHO DE GOIÂNIA</value>
                        <value>2ª VARA DO TRABALHO DE RIO VERDE</value>
                        <value>2ª VARA DO TRABALHO DE ANÁPOLIS</value>
                        <value>11ª VARA DO TRABALHO DE GOIÂNIA</value>
                        <value>VARA DO TRABALHO DE JATAÍ</value>
                        <value>VARA DO TRABALHO DE PIRES DO RIO</value>
                        <value>3ª VARA DO TRABALHO DE ANÁPOLIS</value>
                    </values>
                    <columns mappingId="0">
                        <column id="0" type="String">Nome Orgao Estatistica</column>
                    </columns>
                </lov>
            </info>
        </answer>
    </parameter>
    <parameter optional="true" type="prompt" dpId="DP16">
        <id>1</id>
        <technicalName>Rito</technicalName>
        <name>Rito</name>
        <answer constrained="true" type="Text">
            <info cardinality="Single" keepLastValues="true">
                <lov hierarchical="false" partial="false" refreshable="true" searchable="true" mandatorySearch="false">
                    <id>UNIVERSELOV_DS3.DOf</id>
                    <updated>2016-09-21T13:40:01.000-03:00</updated>
                    <values>
                        <value>SUMARÍSSIMO</value>
                        <value>ORDINÁRIO</value>
                    </values>
                    <columns mappingId="0">
                        <column id="0" type="String">Nome Rito</column>
                    </columns>
                </lov>
                <values>
                    <value id="0">SUMARÍSSIMO</value>
                </values>
            </info>
            <values>
                <value id="0">SUMARÍSSIMO</value>
            </values>
        </answer>
    </parameter>
    <parameter optional="true" type="prompt" dpId="DP17">
        <id>2</id>
        <technicalName>Data inicial:</technicalName>
        <name>Data inicial:</name>
        <answer constrained="false" type="DateTime">
            <info cardinality="Single" keepLastValues="true">
                <previous>
                    <value>2014-12-31T22:00:00.000-02:00</value>
                </previous>
            </info>
            <values>
                <value>2014-12-31T22:00:00.000-02:00</value>
            </values>
        </answer>
    </parameter>
    <parameter optional="true" type="prompt" dpId="DP17">
        <id>3</id>
        <technicalName>Data final:</technicalName>
        <name>Data final:</name>
        <answer constrained="false" type="DateTime">
            <info cardinality="Single" keepLastValues="true">
                <previous>
                    <value>2015-01-30T22:00:00.000-02:00</value>
                </previous>
            </info>
            <values>
                <value>2015-01-30T22:00:00.000-02:00</value>
            </values>
        </answer>
    </parameter>
</parameters>

Could any one help?

[daniel_paulsen]

Hi Hugo,

I don't see anything wrong with the request, so investigatine Locales may be a valid step.

Log into launchpad (same user as in your application) and click on "Preferences"

in "Locales and Time Zone" and try setting "EN_US".

Then try your app again to see if this fixed it.

If this does fix it, what Locale were you using?  I could try testing here to see what's wrong with the format.

Dan

[eric_festinger]

hi Hugo

Please do try:

...

<parameter optional="true" type="prompt" dpId="DP17"> 

<id>3</id> 

  <technicalName>Data final:</technicalName> 

  <name>Data final:</name> 

  <answer type="DateTime"> 

  <values> 

  ...

eric

[former_member197386]

You can check the used format here:

http://www.w3.org/TR/xmlschema-2/#isoformats

Regards,

Anthony

[daniel_paulsen]

Hi Hugo,

Check the value used in the scheduled instance by looking at the history in BI Launchpad.  Was the time part changed from 00:00:00 to a different time (which would equal the offset of your current timezone from GMT)?

If this is the case, try passing the time without quotes using the Zulu time format:

<value>31/1/2015T00:00:00Z</value>

if you want to include the offset for your timezone (eg PST=GMT - 08hrs), then use the following format:

<value>31/1/2015T00:00:00-08:00</value>

There was an issue with the offset being ignored in earlier versions of BI4.1 and it was corrected in BI4.1 SP05 Patch8, SP06 Patch1 and SP07.

See SAP Note 2185370 for details.

Dan