SAP Knowledge Base Article - Public

2890755 - Data Action generate error "Execution of EPM command failed. The error has been logged"

Symptom

  • Existing data action no longer works and generates the error."An unexpected technical error occurred and has been logged. Please contact SAP for further assistance."
  • Issue occurs for all users.
  • Error persists even if the data action is restricted to a single timeperiod and other MEMBERSET dimension restrictions are set.


Stack message:

Execution of EPM command failed. The error has been logged.

ExecutionException@/sap/fpa/services/planSeq/executor/ExecutionException.xsjslib:10
ExecutionManager.prototype._checkResult@/sap/fpa/services/planSeq/executor/ExecutionManager.xsjslib:978
ExecutionManager.prototype._executeEPMModelCommand@/sap/fpa/services/planSeq/executor/ExecutionManager.xsjslib:1211
ExecutionManager.prototype._cleanUpFailedExecution@/sap/fpa/services/planSeq/executor/ExecutionManager.xsjslib:1035
ExecutionManager._handleExecutionFailed@/sap/fpa/services/planSeq/executor/ExecutionManager.xsjslib:433
ExecutionManager.executeBatch@/sap/fpa/services/planSeq/executor/ExecutionManager.xsjslib:1168
ExecutionManager.prototype.executeBatches/<@/sap/fpa/services/planSeq/executor/ExecutionManager.xsjslib:214
ExecutionManager.prototype.executeBatches@/sap/fpa/services/planSeq/executor/ExecutionManager.xsjslib:214
ExecutionManager.prototype.execute@/sap/fpa/services/planSeq/executor/ExecutionManager.xsjslib:201
PlanningSequence._executeValidatedSequence@/sap/fpa/services/planSeq/PlanningSequenceManager.xsjslib:1204
PlanningSequence.prototype.execute@/sap/fpa/services/planSeq/PlanningSequenceManager.xsjslib:882
callFunction@/sap/fpa/services/bo/EpmObjectManager.xsjslib:2329
RpcObject.prototype._callRpc@/sap/fpa/services/core/rest/RestUtil.xsjslib:72
RpcObject.prototype.invoke@/sap/fpa/services/core/rest/RestUtil.xsjslib:26
handleRequest@/sap/fpa/services/GetResponse.xsjslib:157
main@/sap/fpa/services/GetResponse.xsjslib:198
@/sap/fpa/services/GetResponse.xsjs:9

Environment

SAP Analytics Cloud 2019.21

Reproducing the Issue

Run exisiting Data Action

Cause

The problem is caused by a member ID with a single quote(') in the name, like Frank's or Pharmaceuticals Int'l

Resolution

  • This issue will be fixed in a later release
  • In the meanwhile as a workaround please delete any single quotes in dimension descriptions

See Also

Your feedback is important to help us improve our knowledge base.

Keywords

SAP Cloud for Planning, sc4p, c4p, cforp, cloudforplanning, Cloud for Analytics, Cloud4Analytics, CloudforAnalytics, Cloud 4 Planning, BOC, SAPBusinessObjectsCloud, BusinessObjectsCloud, BOBJcloud, BOCloud., SAC, SAP AC, Cloud-Analytics, CloudAnalytics, SAPCloudAnalytics,Error, Issue, System, Data, User, Unable, Access, Sac, Acquisition, Model, Connect, Story, Tenant, Import, Failed, Using, Working , KBA , LOD-ANA-PL , Planning , Problem

Product

SAP Analytics Cloud 1.0