7 Caller 70 is missing.
7.1 Why does the error occur?
• This error normally occurs whenever BW encounters error and is not able to classify
them. There
could be multiple reasons for the same
o Whenever we are loading the Master Data for the first time, it creates SID’s. If system is
unable to create SID’s for the records in the Data packet, we can get this error message.
o If the Indexes of the cube are not deleted, then it may happen that the system may give
the
caller 70 error.
o Whenever we are trying to load the Transactional data which has master data as one of
the
Characteristics and the value does not exist in Master Data table we get this error. System
can have difficultly in creating SID’s for the Master Data and also load the transactional
data.
o If ODS activation is taking place and at the same time there is another ODS activation
running parallel then in that case it may happen that the system may classify the error as
caller 70. As there were no processes free for that ODS Activation.
o It also occurs whenever there is a Read/Write occurring in the Active Data Table of ODS.
For example if activation is happening for an ODS and at the same time the data loading is
also taking place to the same ODS, then system may classify the error as caller 70.
o It is a system error which can be seen under the “Status” tab in the Job over View.
7.2 What happens when this error occur?
• The exact error message is “System response "Caller 70" is missing”.
• It may happen that it may also log a short dump in the system. It can be checked at
"Environment ->
Short dump -> In the Data Warehouse".
7.3 What can be the possible actions to be carried out?
• If the Master Data is getting loaded for the first time then in that case we can reduce
the Data
Package size and load the Info Package. Processing sometimes is based on the size of Data
Package. Hence we can reduce the data package size and then reload the data again. We
can also
try to split the data load into different data loads
• If the error occurs in the cube load then we can try to delete the indexes of the cube
and then reload
the data again.
• If we are trying to load the Transactional and Master Data together and this error occurs
then we can
reduce the size of the Data Package and try reloading, as system may be finding it difficult
to create
SID’s and load data at the same time. Or we can load the Master Data first and then load
Transactional Data
• If the error is happening while ODS activation cause of no processes free, or available for
processing
the ODS activation, then we can define processes in the T Code RSCUSTA2.
• If error is occurring due to Read/Write in ODS then we need to make changes in the
schedule time of
the data loading.
• Once we are sure that the data has not been extracted completely, we can then go
ahead and delete
the red request from the manage tab in the InfoProvider. Re-trigger the InfoPackage
again.
• Monitor the load for successful completion, and complete the further loads if any in the
Process
Chain.