1560922 - "It was not possible to connect to the server ABAP" Work Status error in BPC 7.5 NW | SAP Knowledge Base Article

SAP Knowledge Base Article - Preview

1560922 - "It was not possible to connect to the server ABAP" Work Status error in BPC 7.5 NW

Symptom

  • When trying to set the "Work Status" in BPC for NetWeaver web administration, error "It was not possible to connect to the server ABAP" is returned.
  • ST22 ABAP dump error is seen as follows:
    |    "SAPSQL_INVALID_FIELDNAME" "CX_SY_DYNAMIC_OSQL_SEMANTICS"                                  
    |    "CL_UJW_WORK_STATUS_DAO========CP" or "CL_UJW_WORK_STATUS_DAO========CM00R"                
    |    "GET_REGION_LOCK_INFO"
  • SM21 System log shows error: "Run-time error SAPSQL_INVALID_FILENAME occurred". 

Read more...

Environment

SAP Business Planning and Consolidation (BPC) version 7.5 for NetWeaver (NW) platform.

Keywords

function, module, UJW_API_GET_CURRENT_WS_LCKS, failing, method, GET_REGION_LOCK_INFO, temporary, misses, statuses, workstatus, workstate, It was not possible to connect to the server ABAP, SAPSQL_INVALID_FIELDNAME, CX_SY_DYNAMIC_OSQL_SEMANTICS, CL_UJW_WORK_STATUS_DAO. , KBA , EPM-BPC-NW , NetWeaver Version , How To

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.