Xml Load Error When Setting Up Pov In Ad Hoc Smart View (Doc ID 1327918.1)

Applies to:
Hyperion Financial Management – Version: and later [Release: 11.1 and later ]
Information in this document applies to any platform.


When trying to browse the Point of View (POV) in an Adhoc Query in Smart View you get an error message that reads “XML Load Error: Whitespace is not allowed at this location.”

Your HFM applications includes a Member List whose name contains an ampersand. Owing to a bug, the ampersand is not correctly encoded for XML.

For example:

<filter decompose=”\{OC: Central & Eastern Europe\}” compose=”{OC: Central & Eastern Europe}” name=”OC: Central &amp; Eastern Europe” id=”14″ ></filter>

Note that the name attribute is correctly encoded but the compose and decompose attributes are not.
This issue has been logged as Bug 12626853 – “XML LOAD ERROR: WHITESPACE IS NOT ALLOWED AT THIS LOCATION” WITH AMPERSANDS. This bug is not published.

Avoid ampersands in Member List names, e.g. change ‘Corporate & Other’ into
‘Corporate + Other’ or ‘Corporate and Other’.

This entry was posted in Oracle EPM, Oracle Hyperion Financial Management, Oracle Hyperion Smart View and tagged , , . Bookmark the permalink.

One Response to Xml Load Error When Setting Up Pov In Ad Hoc Smart View (Doc ID 1327918.1)

  1. Azmat Bhatti says:

    Try this and it worked for me

    Please clear the USERPARAMS table for one of the problematic user and see if that helps.

    Note**: Please take a backup of the database before proceeding the actions below.

    1) Ask the user to logoff from HFM, Workspace, SharedServices if any related to Hyperion.
    2) Run the below mentioned query in your SQL Server of HFM database

    Execute the below query on HFM database:

    SELECT * FROM _USERPARAMS WHERE Username like ‘@%’
    (Replace with Application Name, with the problamatic user name)

    Now run the DELETE query
    DELETE FROM _USERPARAMS WHERE Username like ‘@%’
    (Which deletes all the saved parameters from the database)

    3) Ask the user to login and check whether he is still getting the error message.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s