SAP Business Objects Error Messages from Error EPM 02001 to EPM 02004
Cannot parse analytic XML. (EPM 02001)
Cause The analytic is not parsing correctly.
Action Recreate the analytic.
Invalid analytic token. (EPM 02002)
Cause The analytic cannot be retrieved.
Action Logout and then log in again. Try to retrieve the analytic.
If the error message appears again, contact your IT administrator.
Could not find Pareto. (EPM 02003)
Cause The metricor measureon whichthe Paretochart isbasedcouldnotbefound.
Action Check in the analytic definition that the metrics and measures used for the
chart are valid
Cannot find the appropriate metric to drill down. (EPM 02004)
Cause The metric could not be found.
Action Check the analytic’s parameters to verify that the metric exists.
Above are list of SAP Business Objects Error Messages from Error EPM 02001 to EPM 02004 received while performing certain operation against SAP Business Objects Business Intelligence Suite or related products.
What are SAP Business Objects Error Messages?
There are many different types of error messages received while using SAP Business Objects Business Intelligence Suite which include Administration (ADM) Errors,
Administration Wizard (ADW) Errors, BI Platform Servers (FWB) Errors , BIP Framework Middleware (FWM) Errors , Security (USR) Errors, Crystal Reports Errors, Dashboard and Analytics (EPM) Errors, Data Access Errors, Document and Universe Exchange Errors, Enterprise Application Errors, GUI Errors, Import Wizard (IWZ) Errors, List of Values Errors, SAP Live Office (LO) Errors, Metadata Bridges and Universe Builder (MDB) Errors, Publishing (FBE) Errors, Process Tracker (PT) Errors, SAP Query as a Web Service (QWS) Errors, Report Conversion Tool (RCT) Errors, Setup Errors , Translation Manager (UTM) Errors, Universe Errors, Voyager Errors, Web Intelligence Errors, HTTP errors.
Hope this was helpful.
Information about SAP Business Objects Error Messages or Warning Messages on Windows and Linux Operating Systems.