My Oracle Support Banner

12c BI Publisher Reports Errors At UpdateDynamicReportParameters On SOAP Web Service and in Data Model Because SYSDATE is Not Passed Properly (Doc ID 2378073.1)

Last updated on MARCH 23, 2018

Applies to:

BI Publisher (formerly XML Publisher) - Version 12c to 12c [Release 12.0]
Information in this document applies to any platform.

Symptoms

12c BI Publisher reports get an error NullPointerException at updateDynamicReportParameters when submitted via scheduleReport web service through SOAP.

http://<hostname:port>/xmlpserver/servlet/viewHistory?report_url=<path to report>.xdo

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:v2="http://xmlns.oracle.com/oxp/service/v2">
<soapenv:Header/>
<soapenv:Body>
<v2:scheduleReport>
<v2:scheduleRequest>
<v2:deliveryChannels>
<v2:ftpOptions>
</v2:ftpOptions>
</v2:deliveryChannels>
<v2:reportRequest>
<v2:attributeFormat>pdf</v2:attributeFormat>
<v2:attributeLocale>en-us</v2:attributeLocale>
<v2:attributeTemplate>sysdate</v2:attributeTemplate>
<v2:parameterNameValues>
<v2:listOfParamNameValues>
<v2:item>
<v2:name>pLastWeek</v2:name>
<v2:values>
<v2:item>{$sysdate()-7$}</v2:item>
</v2:values>
</v2:item>
<v2:item>
<v2:name>pToday</v2:name>
<v2:values>
<v2:item>{$SYSDATE()$}</v2:item>
</v2:values>
</v2:item>
</v2:listOfParamNameValues>
</v2:parameterNameValues>
<v2:reportAbsolutePath>report path</v2:reportAbsolutePath>
</v2:reportRequest>
<v2:saveDataOption>false</v2:saveDataOption>

<v2:saveOutputOption>true</v2:saveOutputOption>

<v2:scheduleBurstringOption>false</v2:scheduleBurstringOption>
<v2:schedulePublicOption>true</v2:schedulePublicOption>
<v2:startDate></v2:startDate>
<v2:userJobName>sysdate</v2:userJobName>
</v2:scheduleRequest>
<v2:userID>userid</v2:userID>
<v2:password>userpasswordr</v2:password>
</v2:scheduleReport>
</soapenv:Body>
</soapenv:Envelope>

Submit job.

Job submits successfully.

However date value shows {$SYSDATE()-7$}.

When submitting a report through the data model the same results occur of the date is not defined in the data model.



Full message is as follows in the bipublisher.log file:

  

  

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.