Basis Errors and Solutions

Symptom
The system does not return any return code if you call one of the following methods:
CL_HTTP_SERVER=>SERVER_CACHE_UPLOAD( )
CL_HTTP_SERVER=>SERVER_CACHE_INVALIDATE( )
CL_HTTP_SERVER=>SERVER_CACHE_INVALIDATE_ALL( )
CL_HTTP_SERVER=>SERVER_CACHE_INVALIDATE_LIST( )
As a result, applications that use the aforementioned methods do not have the option of handling or catching return codes correctly.
Other terms
ICM, CL_HTTP_SERVER, SERVER_CACHE_UPLOAD, c_last_error
Reason and Prerequisites
This problem is caused by an error during the [...]

Symptom
You get a java.lang.NullPointerException in method com.sap.engine.services.orpersistence.core.PersistenceContextImpl.executeQuery. The exception occurs rarely and is difficult to reproduce.
Other terms
JPA JPQL
Reason and Prerequisites
Prerequisite:
You are using SAP JPA and have the query result cache enabled by setting the hint “com.sap.jpa.cache.query-result” on value “cached” for at least one query.
The exception is caused by an error in SAP’s JPA implementation.
Solution
The [...]

Symptom
You encounter incorrect results for a BW query using FEMS logic
Other terms
BIA, BWA, Accelerator, wrong data, different result
Reason and Prerequisites
Prerequisites:
SAP NetWeaver BW Accelerator Revision 51 or previousThe index for the F-table is not splitThe BWA OLAP index is located on a different TREX index server than the F-table indexYou are running a query that uses [...]

Symptom
You obtain incorrect query results but if you execute the query again the result is correct.
Other terms
BIA, BWA, Accelerator, wrong result, different, rollup, commit, changerun
Reason and Prerequisites
Prerequisites:
SAP NetWeaver BW Accelerator Revision 51 or previousThe query is running on a BWA index when a rollup for that index is activeThe query is running when the commit [...]

Symptom
You experience incorrect query results.
Other terms
BIA, BWA, Accelerator, different, wrong result, kidsel, inconsistent
Reason and Prerequisites
Prerequisites:
SAP NetWeaver BW Accelerator Revision 51 or previousThe fact table index used for the query is not splitThe fact table index is located on the same TREX index server as the OLAP indexAn intermediate internal result exceeds 5 million entries
Reason:Due to [...]

Symptom
You encounter incorrect results for a BW query using FEMS logic
Other terms
BIA, BWA, Accelerator, wrong data, different result
Reason and Prerequisites
Prerequisites:
SAP NetWeaver BW Accelerator Revision 51 or previousThe index for the F-table is not splitThe BWA OLAP index is located on a different TREX index server than the F-table indexYou are running a query that uses [...]

Symptom
You receive incorrect data for queries where the F-table has attributes of type DATE or TIME. You find the following entry in the trace of TREXIndexServer: “Attribute engine function not implemented (index attribute flags ) getAggregateMeasures”
Other terms
BWA, BIA, Accelerator, wrong result, date, time, not implemented
Reason and Prerequisites
Prerequisite: SAP NetWeaver [...]