SAP Knowledge Base Article - Preview

2339354 - Work Orders WOs are not downloading for only 2 users but works for others - due to a /SYCLO/CL_CORE_MDW_USER issue - SAP Work Manager

Symptom

  • The synchronization is made normally however we do not get Work Orders on the SAP Work Managager mobile application for only 2 users (The others are downloading WO correctly)
  • Running SAP SLG1 transaction gives you generic information but nothing really satisfatory to indentify the issue in detail
    • Example SLG1 message: @5D\QAdvertência@ 13.06.2016 13:48:55 USERNAME ( ) +\CLASS=/SYCLO/CL_CORE_MDW_USER
    • Basis/IT team can see something related to the class /SYCLO/CL_CORE_MDW_USER but the message is not conclusive (See below) 

      aa.png
  • Logs show the following for users that has issue:

    ~~~~~~~~~~~Start~~~~~~~~~~~~~~
    2016 06 07 17:54:21#0-300#INFO#System.out###Agentry SAPWM Worker Thread########create::Function /SMERP/PM_DOWORKORDER_GET created |
    2016 06 07 17:54:21#0-300#INFO#System.out###Agentry SAPWM Worker Thread########setImportParameters::COMMIT_WAIT=X |
    2016 06 07 17:54:21#0-300#INFO#System.out###Agentry SAPWM Worker Thread########setImportParameters::MOBILE_USER=MOBILE_USER |
    2016 06 07 17:54:21#0-300#INFO#System.out###Agentry SAPWM Worker Thread########setImportParameters::USER_GUID=B889059BF6A71ED68B96EC96BB4C5BAB |
    2016 06 07 17:54:21#0-300#INFO#System.out###Agentry SAPWM Worker Thread########setImportParameters::MIDDLEWARE_CALL=X |
    2016 06 07 17:54:21#0-300#INFO#System.out###Agentry SAPWM Worker Thread########setParameters::begin |
    2016 06 07 17:54:21#0-300#INFO#System.out###Agentry SAPWM Worker Thread########setFilterRange::filter.setRange for IT_EMPLOYEE_ID_RA=I EQ 00104859 0 |
    2016 06 07 17:54:21#0-300#INFO#System.out###Agentry SAPWM Worker Thread########setParameters::IT_EMPLOYEE_ID_RA LOW=00104859 |
    2016 06 07 17:54:21#0-300#INFO#System.out###Agentry SAPWM Worker Thread########execute::::MOBILE_USER::before BAPI execute: /SMERP/PM_DOWORKORDER_GET |
    2016 06 07 17:54:21#0-300#INFO#System.out###Agentry SAPWM Worker Thread########execute::begin |
    2016 06 07 17:54:21#0-300#INFO#System.out###Agentry SAPWM Worker Thread########validateDestination::begin |
    2016 06 07 17:54:30#0-300#INFO#System.out###Agentry SAPWM Worker Thread########execute::::MOBILE_USER::after BAPI execute: /SMERP/PM_DOWORKORDER_GET |
    2016 06 07 17:54:30#0-300#INFO#System.out###Agentry SAPWM Worker Thread########checkForErrors::1::message ID::I:: - 000 |
    2016 06 07 17:54:30#0-300#INFO#System.out###Agentry SAPWM Worker Thread########checkForErrors::1::message::I::NnhDdEncontr. |
    2016 06 07 17:54:30#0-300#INFO#System.out###Agentry SAPWM Worker Thread########processResults::begin |
    2016 06 07 17:54:30#0-300#INFO#System.out###Agentry SAPWM Worker Thread########processResults::total valid workorders: 0 |
    2016 06 07 17:54:30#0-300#INFO#System.out###Agentry SAPWM Worker Thread########processResults::updatedWorkorders.size=0 |
    2016 06 07 17:54:30#0-300#INFO#System.out###Agentry SAPWM Worker Thread########processResults::validWorkorders.size=0 |
    2016 06 07 17:54:30#0-300#INFO#System.out###Agentry SAPWM Worker Thread########processResults::Update Date/Time from SAP: 06/07/2016 14:53:58 |
    2016 06 07 17:54:30#0-300#INFO#System.out###Agentry SAPWM Worker Thread########run::done |
    2016 06 07 17:54:30#0-300#INFO#System.out###Agentry SAPWM Worker Thread########User::getClientDeviceLanguage::begin |
    2016 06 07 17:54:30#0-300#INFO#System.out###Agentry SAPWM Worker Thread########Steplet::doSteplet() |
    2016 06 07 17:54:30#0-300#INFO#System.out###Thread-7028########Reset timer. |
    2016 06 07 17:54:30#0-300#INFO#System.out###Agentry SAPWM Worker Thread########run::begin |
    2016 06 07 17:54:30#0-300#INFO#System.out###Thread-7028########Session timer sleeping for 60 seconds. |
    2016 06 07 17:54:30#0-300#INFO#System.out###Agentry SAPWM Worker Thread########BAPI::begin |
    2016 06 07 17:54:30#0-300#INFO#System.out###Agentry SAPWM Worker Thread########getFunction::begin |
    2016 06 07 17:54:30#0-300#INFO#System.out###Agentry SAPWM Worker Thread########getFunction::/SYCLO/CORE_USER_PUSH_Q_CLEAR |
    2016 06 07 17:54:30#0-300#INFO#System.out###Agentry SAPWM Worker Thread########validateDestination::begin |
    2016 06 07 17:54:32#0-300#INFO#System.out###Agentry SAPWM Worker Thread########create::Function /SYCLO/CORE_USER_PUSH_Q_CLEAR created |
    2016 06 07 17:54:32#0-300#INFO#System.out###Agentry SAPWM Worker Thread########setParameters::begin |
    2016 06 07 17:54:32#0-300#INFO#System.out###Agentry SAPWM Worker Thread########setImportParameters::TIMESTAMP_FROM_MOBILE=20160607205430 |
    2016 06 07 17:54:32#0-300#INFO#System.out###Agentry SAPWM Worker Thread########setImportParameters::COMMIT_WAIT=X |
    2016 06 07 17:54:32#0-300#INFO#System.out###Agentry SAPWM Worker Thread########setImportParameters::MOBILE_USER=MOBILE_USER |
    2016 06 07 17:54:32#0-300#INFO#System.out###Agentry SAPWM Worker Thread########setImportParameters::USER_GUID=B889059BF6A71ED68B96EC96BB4C5BAB
    ~~~~~~~~~~~End~~~~~~~~~~~~~~~
  • Logs show the following for users without issue

    ~~~~~~~~~~~Start~~~~~~~~~~~~~~
    2016 06 08 10:23:25#0-300#INFO#System.out###Agentry SAPWM Worker Thread########create::Function /SMERP/PM_DOWORKORDER_GET created |
    2016 06 08 10:23:25#0-300#INFO#System.out###Agentry SAPWM Worker Thread########setImportParameters::COMMIT_WAIT=X |
    2016 06 08 10:23:25#0-300#INFO#System.out###Agentry SAPWM Worker Thread########setImportParameters::MOBILE_USER=MOBILE_USER |
    2016 06 08 10:23:25#0-300#INFO#System.out###Agentry SAPWM Worker Thread########setImportParameters::USER_GUID=B889059BF6A71ED68B8363181CC8DBAB |
    2016 06 08 10:23:25#0-300#INFO#System.out###Agentry SAPWM Worker Thread########setImportParameters::MIDDLEWARE_CALL=X |
    2016 06 08 10:23:25#0-300#INFO#System.out###Agentry SAPWM Worker Thread########setParameters::begin |
    2016 06 08 10:23:25#0-300#INFO#System.out###Agentry SAPWM Worker Thread########setFilterRange::filter.setRange for IT_EMPLOYEE_ID_RA=I EQ 00108246 0 |
    2016 06 08 10:23:25#0-300#INFO#System.out###Agentry SAPWM Worker Thread########setParameters::IT_EMPLOYEE_ID_RA LOW=00108246 |
    2016 06 08 10:23:25#0-300#INFO#System.out###Agentry SAPWM Worker Thread########execute::::MOBILE_USER::before BAPI execute: /SMERP/PM_DOWORKORDER_GET |
    2016 06 08 10:23:25#0-300#INFO#System.out###Agentry SAPWM Worker Thread########execute::begin |
    2016 06 08 10:23:25#0-300#INFO#System.out###Agentry SAPWM Worker Thread########validateDestination::begin |
    2016 06 08 10:24:16#0-300#INFO#System.out###Agentry SAPWM Worker Thread########execute::::MOBILE_USER::after BAPI execute: /SMERP/PM_DOWORKORDER_GET |
    2016 06 08 10:24:16#0-300#INFO#System.out###Agentry SAPWM Worker Thread########processResults::begin |
    2016 06 08 10:24:16#0-300#INFO#System.out###Agentry SAPWM Worker Thread########processResults::total valid workorders: 3 |
    2016 06 08 10:24:16#0-300#INFO#System.out###Agentry SAPWM Worker Thread########processResults::updatedWorkorders.size=3 |
    2016 06 08 10:24:16#0-300#INFO#System.out###Agentry SAPWM Worker Thread########processResults::validWorkorders.size=3 |
    2016 06 08 10:24:16#0-300#INFO#System.out###Agentry SAPWM Worker Thread########processResults::Update Date/Time from SAP: 06/08/2016 07:23:24 |
    2016 06 08 10:24:16#0-300#INFO#System.out###Agentry SAPWM Worker Thread########setParts::begin |
    2016 06 08 10:24:16#0-300#INFO#System.out###Agentry SAPWM Worker Thread########setParts::last update with format: 01/01/0000 00:00:01 |
    2016 06 08 10:24:16#0-300#INFO#System.out###Agentry SAPWM Worker Thread########setParts::Number of rows: 2 |
    2016 06 08 10:24:16#0-300#INFO#System.out###Agentry SAPWM Worker Thread########setOperations::begin |
    2016 06 08 10:24:16#0-300#INFO#System.out###Agentry SAPWM Worker Thread########setOperations::Number of rows: 3 |
    2016 06 08 10:24:16#0-300#INFO#System.out###Agentry SAPWM Worker Thread########setOperations::Passing operation object 0030004476400020 to retrieval operation array |
    2016 06 08 10:24:16#0-300#INFO#System.out###Agentry SAPWM Worker Thread########setNotifications::begin |
    2016 06 08 10:24:16#0-300#INFO#System.out###Agentry SAPWM Worker Thread########setNotifications::Number of rows: 1 |
    2016 06 08 10:24:16#0-300#INFO#System.out###Agentry SAPWM Worker Thread########setHistory::begin |
    ~~~~~~~~~~~End~~~~~~~~~~~~~~~


Read more...

Environment

  • SAP Work Manager 6.2.0
  • SAP Mobile Platform SDK 3.0 SP09 

Product

SAP ERP 6.0 ; SAP Mobile Platform 3.0 ; SAP Mobile Platform SDK 3.0 ; SAP Work Manager 6.2.0

Keywords

"SAP Work Manager Workorders are not downloaded", "SAPWM WO missing", "SAP Work Manager WO not seen in device" , KBA , MOB-SYC-SAP , Syclo Mobility for SAP backend , Problem

About this page

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

Search for additional results

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