Extract-Related Problems 

Problem

No data is available in the client after synchronization or no data is extracted on triggering extract.

Case 1: No data available is available in pending extracts after initial or delta download of data from back-end system. In this case Synchronous Extract is not configured.

Case 2: No data is available in the client after initial or delta download of data from back-end system when Synchronous Extract is configured.

This is valid only if any receivers are subscribed and if there is a valid data for the subscriptions.

Analysis

...

       1.      Check whether the required DMSWCV is assigned to the receivers:

                            a.      In the SAP NetWeaver Mobile Administrator, choose Administration  → Device Administration and search for the required device

                            b.      In the search results list, choose the device name.

                            c.      On the Device Management page, go to the Distribution Model Software Component Version tab and check whether the DMSWCV is assigned. If it is assigned, check whether the DMSWCV is operational. The DMSWCV must be operational for the data to be extracted.

       2.      In the SAP NetWeaver Mobile Administrator, choose Administration  → Distribution Rule Administration and check whether the rules of the DM are active or not:

                            a.      In the Distribution Rule Administration, filter all the rules for the DMSWCV and check the activation status.

                            b.      If there is any inactive rule, activate it.

       3.      In the SAP NetWeaver Mobile Administrator, choose Monitoring  →  Queue Monitoring and search for RR queues and Extract queues. Each of these queues must be in the RUNNING state. If they are not, this could be due to one of the following reasons:

¡        Queues may be in READY state but not picked by the queue scheduler for running. In this case, start transaction SMQR and check whether the queue is registered or not. If it is registered, then possibly the queue scheduler is unable to pick the queue.

¡        The queue may be in the SYSFAIL state. Some system level exception can cause this. Retrieve the runtime error trace and contact development support.