Backend showing blank on Work Manager 6.2

[Former Member]

Hello, im having issues deploying the Work Manager 6.2 on SMP 3.0. Ive followed the guide up to the point in which you have to select the .zip deployment file. After that i should be able to see the Backend tab but its showing blank. Ive restarted the service and its still blank. So i checked the logs and in the event log file i found the following error: JAVA EXCEPTION CAUGHT: com.syclo.agentry.AgentryException: 23.09.2015 12:01:52  - Data Object Assignment for BAPI /SYCLO/CORE_MDW_SESSION1_CRT Not Found! So i went to the SAP GUI to check the Agentry config panel, but in there i couldnt find the Work Manager 6.2 mobile app, i only got the previos version 5.3 that i already had. The SMPFND and SMPERP 610_700 are both correctly installed and with support package 4 the BC set /SMERP/SAP_WORKMGR_62_EHP5_REF : SAP Work Manager 6.2.0 for EHP5 is active the /SMERP/EPH5_EAM_BUS_FUNC switch is active I used the transaction /n/syclo/configpanel to check the BAPI wrappers but i dont see the work manager 62 application. What am i missing? Thanks in advance for your help. Regards Nicolás Navarro

[kevin_xu4 · Accepted solution]

Hi,

Could you please check your backend for the SYCLO/CORE_MDW_SESSION1_CRT.

Please just go to the config panel and select BAPI Wrapper Configuration.

Choose the /SYCLO/BAPI_CORE option and find it.

Open it and goto the assignment option and check if your mobile application is under the MDO assignment list and if the active flag is active.

In the meanwhile, could you please open the javaBE.ini file under the application folder and make sure you have imported the config changes to the client.

Best Regards,

Kevin.

[Former Member · Accepted solution]

Kevin, thanks for your prompt reply.

I´ve checked the BAPI Wrapper config for the SYCLO/CORE_MDW_SESSION1_CRT and i dont see the mapping to the SMW62, i only got my old SWM53 mappings.

Im attaching a screenshot.

As for the JavaBE.ini ive checked this configurations with the install guide, but im posting it so you can see if i missed something. Is there any other section of that file that might help?

Thank you

[REQUIRED_BAPI_WRAPPER]

com.syclo.sap.bapi.LoginCheckBAPI=/SYCLO/CORE_SUSR_LOGIN_CHECK

com.syclo.sap.bapi.RemoteUserCreateBAPI=/SYCLO/CORE_MDW_SESSION1_CRT

com.syclo.sap.bapi.RemoteParameterGetBAPI=/SYCLO/CORE_MDW_PARAMETER_GET

com.syclo.sap.bapi.SystemInfoBAPI=/SYCLO/CORE_SYSTINFO_GET

com.syclo.sap.bapi.ChangePasswordBAPI=/SYCLO/CORE_SUSR_CHANGE_PASSWD

com.syclo.sap.bapi.CTConfirmationBAPI=/SYCLO/CORE_OUTB_MSG_STAT_UPD

com.syclo.sap.bapi.DTBAPI=/SYCLO/CORE_DT_GET

com.syclo.sap.bapi.GetEmployeeDataBAPI=/SMERP/HR_DOEMPLOYEE_DATA_GET

com.syclo.sap.bapi.GetUserDetailBAPI=/SYCLO/CORE_USER_GET_DETAIL

com.syclo.sap.bapi.GetUserProfileDataBAPI=/SYCLO/CORE_USER_PROFILE_GET

com.syclo.sap.bapi.PushStatusUpdateBAPI=/SYCLO/CORE_PUSH_STAT_UPD

com.syclo.sap.bapi.RemoteObjectCreateBAPI=/SYCLO/CORE_MDW_USR_OBJ_CRT

com.syclo.sap.bapi.RemoteObjectDeleteBAPI=/SYCLO/CORE_MDW_USR_OBJ_DEL

com.syclo.sap.bapi.RemoteObjectGetBAPI=/SYCLO/CORE_MDW_SESSION_GET

com.syclo.sap.bapi.RemoteObjectUpdateBAPI=/SYCLO/CORE_MDW_SESSION_UPD

com.syclo.sap.bapi.RemoteReferenceCreateBAPI=/SYCLO/CORE_MDW_USR_KEYMAP_CRT

com.syclo.sap.bapi.RemoteReferenceDeleteBAPI=/SYCLO/CORE_MDW_USR_KEYMAP_DEL

com.syclo.sap.bapi.RemoteReferenceGetBAPI=/SYCLO/CORE_MDW_SESSION_GET

com.syclo.sap.bapi.RemoteReferenceUpdateBAPI=/SYCLO/CORE_MDW_SESSION_UPD

com.syclo.sap.bapi.RemoteSessionDeleteBAPI=/SYCLO/CORE_MDW_SESSION1_DEL

com.syclo.sap.bapi.RemoteUserDeleteBAPI=/SYCLO/CORE_MDW_SESSION1_DEL

com.syclo.sap.bapi.RemoteUserUpdateBAPI=/SYCLO/CORE_MDW_SESSION_UPD

com.syclo.sap.bapi.SignatureCaptureBAPI=/SMERP/CORE_DOBDSDOCUMENT_CRT

[REQUIRED_BAPI_CLASS_MAPPING]

ChangePasswordBAPI=com.syclo.sap.bapi.ChangePasswordBAPI

CTBAPI=com.syclo.sap.bapi.CTBAPI

CTConfirmationBAPI=com.syclo.sap.bapi.CTConfirmationBAPI

DTBAPI=com.syclo.sap.bapi.DTBAPI

GetEmployeeDataBAPI=com.syclo.sap.bapi.GetEmployeeDataBAPI

GetUserDetailBAPI=com.syclo.sap.bapi.GetUserDetailBAPI

GetUserProfileDataBAPI=com.syclo.sap.bapi.GetUserProfileDataBAPI

LoginCheckBAPI=com.syclo.sap.bapi.LoginCheckBAPI

PushClearUserQueueBAPI=com.syclo.sap.bapi.PushClearUserQueueBAPI

PushResetUserQueueBAPI=com.syclo.sap.bapi.PushResetUserQueueBAPI

PushStatusUpdateBAPI=com.syclo.sap.bapi.PushStatusUpdateBAPI

RemoteObjectCreateBAPI=com.syclo.sap.bapi.RemoteObjectCreateBAPI

RemoteObjectDeleteBAPI=com.syclo.sap.bapi.RemoteObjectDeleteBAPI

RemoteObjectGetBAPI=com.syclo.sap.bapi.RemoteObjectGetBAPI

RemoteParameterGetBAPI=com.syclo.sap.bapi.RemoteParameterGetBAPI

RemoteReferenceCreateBAPI=com.syclo.sap.bapi.RemoteReferenceCreateBAPI

RemoteReferenceDeleteBAPI=com.syclo.sap.bapi.RemoteReferenceDeleteBAPI

RemoteReferenceGetBAPI=com.syclo.sap.bapi.RemoteReferenceGetBAPI

RemoteUserCreateBAPI=com.syclo.sap.bapi.RemoteUserCreateBAPI

RemoteUserDeleteBAPI=com.syclo.sap.bapi.RemoteUserDeleteBAPI

SignatureCaptureBAPI=com.syclo.sap.bapi.SignatureCaptureBAPI

SystemInfoBAPI=com.syclo.sap.bapi.SystemInfoBAPI

[mark_pe · Accepted solution]

Juan,

Please confirm that you have installed all the requirements that is needed for SAP Work Manager 6.2.

Our SAP colleague have created a landing page for it. Normally, if you are getting that error above, the backend requirements were not fully installed and activated.

Please see the landing page here.

Double check that you got all the requirements installed.

Regards,

Mark Pe
SAP Platinum Support Engineer

[Former Member · Accepted solution]

Thank for your answer i´ve been going over and over this issue and finally realized i had activated the wrong BC Set, i used the one with EHP5 for Work manager with LAM, and it was the wrong one to use.

Thanks for your help.

[mark_pe · Accepted solution]

Juan,

Thanks for sharing your update.

Best Regards,

Mark Pe

SAP Platinum Support Engineer