cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

SAP ME Configuration for Upgrade Wizard Error

Ankita2198
Newcomer
0 Kudos
274

Hello team,

We have performed a MES system upgrade from 15.4 to 15.5 . Post the upgrade when we are trying to run the wizard SAP ME Configuration for Upgrade Wizard Error . We are getting error.

ReloadInitialDataService.reloadInitialData(): Error occurred while reloading initial data. The error stack trace is: com.sap.me.frame.transitionutils.Exceptions$LegacyBusinessException: Error while parsing the following XML message: "<?xml version="1.0" encoding="UTF-8"?><DX_REQUEST>    <IMPORT ref_check="false" mode="idat">    <BROWSE_ENGINE_RULE_OBJECT>    <!-- SHOP_ORDER -->        <ROW>        <BROWSE_OBJECT_BO>            <BROWSE_OBJECT>SHOP_ORDER</BROWSE_OBJECT>        </BROWSE_OBJECT_BO>        <NAME>PLAN_COMP_DATE_S</NAME>        <ACTIVITY_BO/>        <RULE_TYPE>VALUE</RULE_TYPE>        <TABLE_A>SHOP_ORDER</TABLE_A>        <FIELD_A>PLANNED_COMP_DATE</FIELD_A> ........<OPERATOR>LIKE</OPERATOR>        <VALUE_PATTERN></VALUE_PATTERN>        <DB_TYPE>ALL</DB_TYPE>        <CRITERIA></CRITERIA>    </ROW>    <ROW>        <BROWSE_OBJECT_BO>            <BROWSE_OBJECT>ACTION_ROUTING</BROWSE_OBJECT>        </BROWSE_OBJECT_BO>        <NAME>ROUTER_NC</NAME>        <ACTIVITY_BO>        </ACTIVITY_BO>        <RULE_TYPE>VALUE</RULE_TYPE>        <TABLE_A></TABLE_A>        <FIELD_A></FIELD_A>        <TABLE_B></TABLE_B>        <FIELD_B></FIELD_B>        <OPERATOR></OPERATOR>        <VALUE_PATTERN>ROUTER &lt;&gt; '_SYSTEM'</VALUE_PATTERN>        <DB_TYPE>ALL</DB_TYPE>        <CRITERIA></CRITERIA>    </ROW>    </BROWSE_ENGINE_RULE_OBJECT>    </IMPORT></DX_REQUEST>"; exception is "***Parse Fatal Error***Line: 1, URL: null, Message: The entity name must immediately follow the '&' in the entity reference." (Message 614)

 

Accepted Solutions (0)

Answers (1)

Answers (1)

sergiy_katerinich
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi!

It is a known issue that will be fixed in the next patch by SAP Note 3571559. A preliminary date is March 13. 

Regards,

Sergiy