Work Management

Hi I don't undestand completly the function of work management. I read de manual iut221 but the idea of the module isn't clear. Somebody help me to understand this module, with information of othe material. Thanks
Horace
Moderator note: OP notified of rules of engagement - and look at [sap help for work mgmt|http://help.sap.com/saphelp_erp60/helpdata/en/6a/1a6c35a018d041e10000009b38f839/frameset.htm]
Edited by: William Eastman on Jul 20, 2010 3:31 AM

Similar Messages

Attachments in Work Manager 6.0

Attachments in Work Manager 6.0 work out of the box as far as allowing a user to attach a document, upload and download the document. However, we're not seeing any connection between attachments in WM and the SAP GUI. Attachments added to a Work Order in the SAP GUI are not visible in Work Manager and attachments to the same Work Order in Work Manager are not visible in SAP GUI. How do you adjust the storage of attachments and their visibility?
We're Services for Objects for attachments.
Tags edited by: Michael Appleby

Abhishek,
This may be possible but will depend on the host OS for the mobile device (Windows can do it, iOS can't) as well as how you have your processes defined and if you have the necessary editing tools on the device.
The process will be to download the document to the device.
Launch the editing software passing the file downloaded to edit
Save the file
Attached the edited file to your Work Order
Transmit to upload the edited document.
The reason iOS can't do this is due to the nature of your applications being contained and not sharing data across applications. There may be some iOS OS enhancements coming in 7.2 and beyond which may enable this data sharing but for now you can't do it on iOS without using custom code (OpenUI on SMP3.0)
Android may work depending on where you store you downloaded documents. If they are stored in a "public" area then it might be possible to also do this on Android.
Good luck.
--Bill

SAP Work Manager customization - adding a new field to equipment details screen (Syclo Agentry)

Hi Experts,
I am trying to add a field (NAME1) on the Equipment details screen under work orders in work manager 5.3 application.
I have performed the following steps, but I am getting an error while connecting to the application.
1) Create extension for Equipment class to add a new field.
2) added the new field (Name1) as the property to the standard object Equipment.
3) Added the field on the screen.
4) Added the field (name1) to the complex table ctEquipment.
5) Added the JAR file to Agentry.ini file.
6) Changed the Class mapping for parameter "Equipment" under group "SAPOBJECT" to point it to the custom (Extended) class.
7) Changed the class mapping for complex table parameter "ctEquipment" under group "CT_SAPOBJECT" to point it to the custom class.
8) after publishing the changes and re-starting the server, I get following error.
the log file generated (message.log) also has the same description.
What am I missing here? Any help would be really appreciated.

Hi Emanuel,
Thanks for looking into this issue.
I have performed the following steps as suggested by you, still it doesn't seem to work and gives the same error.
Below are the changes done on the ECC Side.
1) Copied the standard equipment class /SYCLO_CL_PM_EQUIPMENT1_DO to custom class ZSYCLO_CL_PM_EQUIPMENT1_DO. Changes made in the GET Method to get custom equipment related data
2) Modified the standard equipment structure /SYCLO/PM_EQUI_STR by adding one custom field
3) Configured this custom class as the object handler in the equipment mobile data object
4) Configured this custom class as the object handler for the equipment complex table
5) We are still using the standard BAPI Wrapper itself for getting the equipment data and the added field is reflected in the BAPI Wrapper table parameter
Is there something we are missing?

How to publish Work Manager 6.0 on SMP3.0 ?

Hi SCN Community,
I'm trying to get the Work Manager 6.0 running on SMP 3.0 (running on Linux). Currently the events.log within the Agentry folder states, that the Agentry Server was started. But If I look into the Threads*.log I see there might be a problem and I'm also not able to connect to the server.
Unfortunately I couldn't find any manual or post where someone described the steps to get a work manager running on SMP 3.0. The SMP 3.0 server manual as well as the SDK manual just describing in general how to publish an application to the SMP 3.0. But for Work Manager, there might be some special things to be done ...
Any help/hints are welcome!
Here what I did so far:
Install SMP 3.0 up to SP02 on Suse SLES 11
Install SAP JCo 2.1.11 (test successful: java -jar /DVD_HANA/jco/sapjco.jar -stdout )
Create a new application in SMP with type Agentry and select security profile default
Install SMP3.0 SDK SP02 (Agentry)
Setup Eclispe 4.2.2 with Agentry Plugin 7.0.2
Import a Work Manager 6.0 from Teamshare
Export Agentry Project as a production version and point to the Agentry.ini which is in folder /opt/SAP/MobilePlatform3/Server/configuration/com.sap.mobile.platform.server.agentry.application
Include all jar files to the ZIP file
Import the ZIP file within Agentry application in SMP 3.0
Create JavaBE.ini in folder /opt/SAP/MobilePlatform3/Server which is copied from WM6.0 server
Adjust Agentry.ini in folder /opt/SAP/MobilePlatform3/Server/configuration/com.sap.mobile.platform.server.agentry.application (see section config files)
Restart Server
Config files:
Agentry.ini
[Server Administration]
authenticationCertificateStore=AgentryServer.pfx
authenticationCertificateStorePassword=Rzdrj~SwixoAqzmbVxgi
authenticationCertificateStorePasswordEncoded=true
[System Connections]
2=ag3httpxmlbe.dll
1=ag3javabe.dll
[Configuration]
apnsCertificateDirectory=apnsCertificates
apnsCertificatePassword=Rzdrj~SwixoAqzmbVxgi
apnsCertificatePasswordEncoded=True
apnsEnabled=True
applicationGlobalsFile=Globals.ini
applicationStringsFile=ApplicationText.ini
clientStringNamesFile=ClientStringNames.ini
clientStringsFile=ClientText.ini
developmentServer=False
enableFailedTransactionLogging=True
enableOverrideFile=Enables.ini
enableTransactionFailureHandling=False
failedTransactionFilenameFormat=%{userid} %{transaction_name} %{date} %{time}-%{count}.xml
failedTransactionsQueue=FailedTransactionsQueue
gcmEnabled=True
gcmServerAuthorizationKey=Authorization:key=AIzaSyDi0qWQEewdbmNSV_o9QNtSQrlxPnBXtBM
gcmServerLink=https://android.googleapis.com/gcm/send
imagesPath=Application\Development\Images
localizationPath=
localizations=
overrideInfoTableDirectory=OverrideInfoTable
overrideTypesFile=OverrideTypes.ini
postedTransactionDirectory=posted
postedTransactionFile=%{device}.pli
scriptsPath=Application\Development\Scripts
spinDocIniFile=
threadCount=0
transmitConfigurationFile=TransmitConfigurations.ini
trustedCertificateStore=
updateIdleWait=60
updatePeriod=60
urlPath=
[HTTPXML-2]
authenticationCertificateStore=MY
authenticationCertificateStorePassword=
authenticationCertificateStorePasswordEncoded=False
autoDequote=True
baseURL=http://localhost:8282
basicAuthenticationPassword=
basicAuthenticationPasswordEncoded=False
basicAuthenticationUserID=
constantsFile=httpxml_sd.ini
enableAuthentication=False
enablePreviousUserAuthentication=False
httpConnectTimeout=60
httpReceiveTimeout=300
httpResolveTimeout=60
httpSendTimeout=300
listenOn=
name=2
timeZoneName=
timeout=300
trustedCertificateStore=
useSSL=False
xmlNamespaces=
[Java-1]
classPath=./ini4j.jar;./Agentry-v5.jar;./Z_SAPWM-6.0.0.0.jar;./SAPWM-6.0.0.0.jar;./SAPCommon-130881.jar;
constantsFile=
deleteSource=True
enableAuthentication=True
enablePreviousUserAuthentication=True
name=Java-1
outputDirectory=.
performCompile=True
printBusinessLogicStackTrace=False
printStackTrace=False
scriptsPath=
serverClass=com.syclo.agentry.Server
sourceDirectory=.
timeZoneName=
[SpinDoc]
facePath=sql\custom;sql
facepath=sql\custom;sql
[TimeZoneAlias]
Log files:
events.log
02/27/2014 18:51:45, 0,         0,         0, Thr 140352349296384, New files opened events.log, messages.log
02/27/2014 18:51:45, 0,         0,         2, Thr 140352349296384, Agentry Startup
02/27/2014 18:51:45, 0,        17,        14, Thr 140352349296384, WebSockets Front End v7.0.2.151
02/27/2014 18:51:45, 0,         1,         4, Thr 140352349296384, Agentry v7.0.2.151
02/27/2014 18:51:45, 0,        20,       150, Thr 140352200132352, Loading Production application definitions using file "SAPWM-v1-0-0-app"
02/27/2014 18:51:45, 0,        20,       152, Thr 140352200132352, Loading Production application definitions for default localization
02/27/2014 18:52:07, 0,        20,       153, Thr 140352200132352, Finished loading Production application definitions for default localization
02/27/2014 18:52:07, 0,        20,       151, Thr 140352200132352, Finished loading Production application definitions using file "SAPWM-v1-0-0-app"
02/27/2014 18:52:08, 0,        24,         4, Thr 140352349296384, Loaded 2 (HTTPXML v7.0.2.151) from ag3httpxmlbe.dll
02/27/2014 18:52:08, 0,        23,         4, Thr 140352349296384, Loaded Java-1 (Java v7.0.2.151) from ag3javabe.dll
02/27/2014 18:52:08, 0,        20,         4, Thr 140352349296384, Server v7.0.2.151
02/27/2014 18:52:08, 0,        17,        10, Thr 140352349296384, WebSockets Front End v7.0.2.151
02/27/2014 18:52:08, 0,         0,         0, Thr 140352349296384, Old log files moved into /opt/SAP/MobilePlatform3/Server/log/agentry/rolled/2014-02-27-185145
02/27/2014 18:52:08, 0,         0,        23, Thr 140352349296384, Agentry startup is complete.
Thread-140352200132352.log
2014/02/27 18:52:07.310: Opening log file
2014/02/27 18:52:07.310: + Thread=140352200132352
2014/02/27 18:52:07.310:   + Server=Agentry
2014/02/27 18:52:07.310:     + Load Loop=Production
2014/02/27 18:52:07.310:       + AppIniFile=SAPWM-v1-0-0-app
2014/02/27 18:52:07.310:         + Module=PM
2014/02/27 18:52:07.310:           + Service Event=WorkOrderPushHTTPListener
2014/02/27 18:52:07.310:             Failed to load definition for Service Event 'WorkOrderPushHTTPListener'
2014/02/27 18:52:07.310:           + Service Event=WorkorderPushByOperationHTTPListener
2014/02/27 18:52:07.310:             Failed to load definition for Service Event 'WorkorderPushByOperationHTTPListener'
2014/02/27 18:52:07.311:           + Service Event=WorkorderPushBySubOperationHTTPListener
2014/02/27 18:52:07.311:             Failed to load definition for Service Event 'WorkorderPushBySubOperationHTTPListener'
2014/02/27 18:52:07.311:           + Service Event=BDSDocumentPushHTTPListener
2014/02/27 18:52:07.311:             Failed to load definition for Service Event 'BDSDocumentPushHTTPListener'
2014/02/27 18:52:07.311:           + Service Event=DMSDocumentPushHTTPListener
2014/02/27 18:52:07.311:             Failed to load definition for Service Event 'DMSDocumentPushHTTPListener'
2014/02/27 18:52:07.311:           + Service Event=WorkorderPushByMRSHTTPListener
2014/02/27 18:52:07.311:             Failed to load definition for Service Event 'WorkorderPushByMRSHTTPListener'
When trying to connect with the WPF client I get a communication error (14) and nothing is shown in the log files ..
Best Regards,
Michel

Jason,
deleting the service events was helpful regarding the error shown in the Thread log file. After publishing a new version the server seems to start, but has no activity to SAP. I expected at least an initial logon to the SAP system using the service user.
Current log files are:
events.log:
02/28/2014 06:16:36, 0,         0,         0, Thr 140136552040192, New files opened events.log, messages.log
02/28/2014 06:16:36, 0,         0,         2, Thr 140136552040192, Agentry Startup
02/28/2014 06:16:36, 0,        17,        14, Thr 140136552040192, WebSockets Front End v7.0.2.151
02/28/2014 06:16:36, 0,         1,         4, Thr 140136552040192, Agentry v7.0.2.151
02/28/2014 06:16:36, 0,        20,       150, Thr 140136413689600, Loading Production application definitions using file "SAPWM-v1-1-0-app"
02/28/2014 06:16:36, 0,        20,       152, Thr 140136413689600, Loading Production application definitions for default localization
02/28/2014 06:17:06, 0,        20,       153, Thr 140136413689600, Finished loading Production application definitions for default localization
02/28/2014 06:17:06, 0,        20,       151, Thr 140136413689600, Finished loading Production application definitions using file "SAPWM-v1-1-0-app"
02/28/2014 06:17:06, 0,        24,         4, Thr 140136552040192, Loaded HTTP-XML Back End (HTTPXML v7.0.2.151) from ag3httpxmlbe.dll
02/28/2014 06:17:06, 0,        23,         4, Thr 140136552040192, Loaded Java-1 (Java v7.0.2.151) from ag3javabe.dll
02/28/2014 06:17:06, 0,        20,         4, Thr 140136552040192, Server v7.0.2.151
02/28/2014 06:17:07, 0,        17,        10, Thr 140136552040192, WebSockets Front End v7.0.2.151
02/28/2014 06:17:07, 0,         0,         0, Thr 140136552040192, Old log files moved into /opt/SAP/MobilePlatform3/Server/log/agentry/rolled/2014-02-28-061636
02/28/2014 06:17:07, 0,         0,        23, Thr 140136552040192, Agentry startup is complete.
messages.log is empty and Thread*.log doesn't exist anymore.
Any further idea how to get this up and running?
Best Regards,
Michel

Work Manager 6.1 not rendering on ATE iPad

Hi,
Working with Work Manager 6.1 I find the screens aren't rendering for a number of platforms in the ATE. For our current project we are using the iPad screenset but when testing via ATE the screens don't display the data (All the objects are downloaded correctly).
I couldn't find any SAP notes covering the problem.
This makes it difficult to test rules and actions because many are in screens the need to be accessed by drilling into objects. Since the data isn't visible you can't drill into the required screens.
1. Is this a known issue? If so are there plans to fix this?
2. Are there suggested workarounds?
Currently we're using 2 approaches -
a. Temporarily make the rule/action available on the main screens so they can be triggered and debugged.
b. Make the rules/actions available in the Pocket screensets and trigger them from there (Currently only the Windows CE Pocket PC Portrait platform seems to render correctly)
After successfully testing the rule/action, then remove the temp change. Both approaches can be time consuming and fiddly to implement so it would be much better if ATE just rendered the screens properly.
3. Is it possible to increase the tracing for the other Agentry Clients e.g. WPF or Agentry SMP logging so it can output trace information about rules/actions?
Development Environment -
ATE Version - 7.0.3.605
SMP Platform - 3.0.3.2
Cheers,
Stephen

Hi Michael,
My clients are below -
WPF Agentry Client - 7.0.3.605 (this renders correctly shown below)
SMP Platform - 3.0 SP03 PL02 (Not sure where to find the Agentry Sever version embedded in SMP)
ATE - 7.0.3.605
The ATE / Agentry Clients have been downloaded/installed using SMP SDK 3.0 SP04
Searching SCN I found the questions below which state that rendering in the ATE for iPad doesn't work for Agentry 6.1.x. I want to understand if this still applies for v7.x
SAP Work Manager App not displaying in ATE and iPhone
Improper screen in the Ipad and iphone platform in ATE V6.1.0.3
Cheers,
Stephen

Work Manager 6.2 (CS) - Longtext not set for multiplie Notification Activities

Hi all,
I am trying to post multiple activities, each with its own long text from the work manager. The thing is that only the first activity will have the long text. While debugging /SYCLO/IF_CORE_DO_HANDLER~CREATE (/SMERP/CL_CS_NOTIFICATION_DO), I found a curious piece of code, that basically does the following:
Loop over activities (outer loop)
Get a fresh sort number
Loop over long texts (inner loop)if the long text sort number matches the activity sort number (the activity from the outer loop)
then replace the long text sort number by the fresh sort number and remove the long text from the list of long texts and copy its values to another list
else remove the long text from the list of long texts and copy its values to another list
replace the activity sort number (the activity from the outer loop) with the fresh sort number
What happens with multiple activities is that in the inner loop, all the long texts are removed from the list of long texts (even those that are matching the second, third, ... activity in the activity list). Therefore, only for the first activity, long texts are added. Did anyone else encounter this problem (if this is working for anyone, could you provide me with your BAPI parameters)? Any idea on what SAPWM-911 is about (would it be safe to get rid of that part)?
             LOOP AT me->tab_notif_activity ASSIGNING <notif_activity>.
               ADD 1 TO lv_sort_no.
               LOOP AT lt_notif_longtext INTO ls_notif_longtext WHERE objtype = lc_ltext_notif_activity.
                 lv_index = sy-tabix.
                 IF ls_notif_longtext-objkey+4(4) = <notif_activity>-act_sort_no.
                   ls_notif_longtext-objkey+4(4) = lv_sort_no.
                   APPEND INITIAL LINE TO me->tab_notif_longtext ASSIGNING <notif_longtext>.
                   MOVE-CORRESPONDING ls_notif_longtext TO <notif_longtext>.
                   DELETE lt_notif_longtext INDEX lv_index.
                   "<--Ins 332_700 SP1 - SAPWM-911 - Start
                 ELSE.
                   "Check for remaining longtext rows not matching with parent table
                   "is considered as update to the existing activity notes
                   APPEND INITIAL LINE TO me->tab_notif_longtext ASSIGNING <notif_longtext>.
                   MOVE-CORRESPONDING ls_notif_longtext TO <notif_longtext>.
                   DELETE lt_notif_longtext INDEX lv_index.
                   "<--Ins 332_700 SP1 - SAPWM-911 - End
                 ENDIF.
               ENDLOOP.
               <notif_activity>-act_sort_no = lv_sort_no.
             ENDLOOP.
Thanks in advance for any contribution to this problem.
Regards, Daniel

Hi Daniel,
I would suggest you raise an OSS message to get this fixed if you believe its bug.
With Regards
Murali

Work Manager 6.1 - Complex table Enhancement

Hi All,
I had created a custom class for a Complex Table - CodeGroup - which is attached - on top of Work Manager 5.3 Java Code.
Now we are upgrading to SMP 3.0 and Work Manager 6.1, and this class is throwing this error during transmit:
JAVA EXCEPTION CAUGHT: java.lang.AbstractMethodError: Missing implementation of interface method "com.syclo.sap.ComplexTableObject.setProperties(Lcom/syclo/sap/jco/JCO$Table;)V"
I am not sure which method am missing to implement.
Kindly help.
Regards
Ankur
Tags edited by: Michael Appleby

Hi Stephen,
Yes I am using the same call that I had on WM 5.3 on WM 6.1.
How do I implement the changes without having the source code of WM 6.1?
I have been pointed to some documentation by SAP, but it is not helping me much.
Please advice.

Work Manager 6.1: java.lang.reflect.InvocationTargetException

Hi all,
Please, I need your help with this issue. I installed Work Manager 6.1 over SMP 3.0.3.
I added a field to complex table ctCatalogGroup. The field was already contemplated on the backend so I only had to add it in Agentry. It worked fine for a while but suddenly it started giving me this error during transmit every time since then:
My Java class looks like this:
And I added the field in Agentry accordingly:
Config Panel parameters for this are:
The first thing I noticed is this error in the SMP log:
2015/04/23 08:29:12.540: + WorkFunction=00000001496AF658
2015/04/23 08:29:12.540: + User=invpos_out30
2015/04/23 08:29:12.540: + Server=Agentry
2015/04/23 08:29:12.540: + Complex Table=ctcatalogprofile
2015/04/23 08:29:12.540: Update BHT 'ctcatalogprofile' for 'User': Client last data update 12:00:01 a.m. 01/01/1900
2015/04/23 08:29:12.540: Update BHT 'ctcatalogprofile' for 'User': Getting back end connections
2015/04/23 08:29:12.540: client last data update=12:00:01 a.m. 01/01/1900
2015/04/23 08:29:12.540: Backend step is configured as a Java Class; using Java class com.syclo.sap.ComplexTable
2015/04/23 08:29:12.540: Using Java Class com.syclo.sap.ComplexTable for ComplexTable
2015/04/23 08:29:12.555: + BackEnd=Java-SAPJavaConnection
2015/04/23 08:29:12.555: Exception while starting complex table update for table 'ctcatalogprofile': JavaBackEndError: JAVA EXCEPTION CAUGHT: java.lang.reflect.InvocationTargetException in AgentryComplexTableFactory::createComplexTable at AgentryComplexTableFactory.cpp:129
As well as this other one in the events.log:
04/23/2015 08:23:32, 0, 20, 16, Thr 9240, Threads in thread pool 'Runtime' expanded to 2. Adding thread 3580
04/23/2015 08:25:13, 1, 29, 1, Thr 3580, java/net/SocketException, java.net.SocketException: Connection reset by peer: socket write errorAngelJavaStreamsConnection.cpp#189:AngelJavaStreamsConnection::handleException
04/23/2015 08:25:13, 1, 4,3221225477, Thr 3580, EXCEPTION_ACCESS_VIOLATION, 000000018000DE02, 0, R, 0000000000000000, ..\agentry\threadManager.cpp#354:ThreadManager::WorkerThread::function
04/23/2015 08:25:27, 0, 0, 6, Thr 7572, invpos_out30: relogin failed at ANGEL: B4A91958-A9A4-46F8-B323-20C61E7E76E8; attempt from ANGEL: 97E1F7AF-4E38-4ECB-8D3C-2E2D4AFEA2AE
04/23/2015 08:25:56, 0, 0, 6, Thr 7572, invpos_out30: relogin failed at ANGEL: B4A91958-A9A4-46F8-B323-20C61E7E76E8; attempt from ANGEL: 15FAC37B-A017-46AB-B528-B2B4610423CC
04/23/2015 08:26:27, 0, 0, 6, Thr 7572, invpos_out30: relogin failed at ANGEL: B4A91958-A9A4-46F8-B323-20C61E7E76E8; attempt from ANGEL: BFDB1CBE-12D9-4A66-8EBA-A855B2B90D23
04/23/2015 08:29:12, 1, 20, 18, Thr 3580, JAVA EXCEPTION CAUGHT: java.lang.reflect.InvocationTargetException
I would like to know if anyone faced something like this before or any suggestions on how to dig deeper for a solution. What confuses me is that it worked ok at first and now I can no longer start the client. That is as far as I can get.
Best regards!
Leonardo.

Hi,
Can you modify the step
public void setProperties(Table tbl) throws Exception {
        super.setProperties(tbl);
        setShortText(tbl.getString("KURZTEXT")).trim());
to
public void setProperties(Table tbl) throws Exception {
        super.setProperties(tbl);
        setShortText(tbl.getString("KURZTEXT"));
Thanks & Regards,
Sravanthi

Work Manager 6.1: Uploading pictures or documents error

Hi,
I'm working with SMP 3.0 and Work Manager 6.1 for Android platform
I'm trying to attach a picture and/or a document to a Work Order and to a Notification, but when I start the transmit the following error is displayed in the client:
Sending Document Link Picture Add For Work Order...
Unexpected disconnection from server (11)
'Angel' connection failed
I tried to debug the Java but it didn't reach any break point or "catch", I also checked the SMP 3.0 Agentry logs and there is nothing.
I went through the installation notes and documents and I haven't been able to find out if I missed some configuration. I also checked this nice blog http://scn.sap.com/community/mobile/blog/2014/03/25/troubleshooting-sap-work-manager-60-attach-document-issue with no luck.
Can you help me with this?
Thank you in advance
Tags edited by: Michael Appleby

Short update for this issue. I created a SAP incident regarding it.
It's only failing when attaching pictures in Android (iOS works fine), and it seems due a platform bug documented here: http://code.google.com/p/android/issues/detail?id=17535
But since WM 6.1 is supported for Android 4.0 or higher, I expect some help from SAP if the cause is what I think.

Work Manager 6.1 problem with push

Dear community,
We're developing / configuring a Work Manager 6.1 application which communicates with an SMP 3.0 SP 4.
We want to set up push for work orders as well as attachments on work orders.
In the application definitions:
push is enabled on both the Angel and the Angel Lite connection
push definitions for BDSDocumentsPush, DMSDocumentsPush and WorkOrdersPush are polling enabled, currently with a 1 minute interval (for testing purposes)
In configpanel:
Push scenario's are configured
For work order, the exchange object configuration is present
In outbound trigger configuration, the server name, IP address and port are filled. The port is the same as the one configured in the SMP Admin console.
In the mobile object data configuration the push objects (SWM61_BDS_DOCUMENT_PUSH, SWM61_DMS_DOCUMENT_PUSH, SWM61_WORKORDER_PUSH) have "push enabled" checked.
We can observe that the push notifications are getting generated on the backend, because I can see them in the push instance monitor:
For attachments:
For an urgent work order:
For attachments, the status is process with current status new until the moment that you perform a synchronize on the agentry client, however long you wait. After the synchronize is finished, it gets the status completed with current status cancelled.
For work orders, it just gets the status completed, with 0 total recipients, even though I am connected in the agentry client at that time.
In user monitor, I saw that there were no active connections for my user:
But in SMP admin console (around the same time):
Other observations: when I run /SYCLO/CORE_OTRIG_RETRY_PROG on backend server, it only finds outbound triggers for those with status "process", not those with status "completed".
I have also looked at the troubleshooting document: http://scn.sap.com/community/mobile/blog/2014/03/25/troubleshooting-sap-work-manager-60-attach-document-issue, but we are already on SMERP 610_700 SP4.
I could also not find any errors in the SMP server log.
Any advice, additional things I can check, ... are highly appreciated as I currently don't know where to look anymore.
Best regards,
Annelies

Hello,
Yes, the user has the necessary permissions. And now I am sure that the port is open.
I continued testing and now attachments are received via push, but work order pushes still don't come through. I can see them in the monitor, but they always have 0 recipients, even while I am connected. Any suggestions for that?
Kind regards,
Annelies

Work Manager 6 - JCO Version out-of-support

Hi all,
in the comments of JCO 2.1 Table Iterator (for-each-loop) I was made aware, that the JCO version 2.1.8 delivered with the current Work Manager 6.0 is not supported anymore by SAP. Michael Appleby asked me to start a discussion on this in order to give this some more attention. So, here it is...
Regards, Daniel

Daniel,
Currently Work Manager doesn't support SAPJCO 3.0. We have a open request with our Product team to look into this. You can contact support about: SPS-271 - Support for SAPJCO 3.0
Stephen

Work Manager 6.1 New field - Read only

Hi,
I'm attempting to add a new field for CATS time posting in Work Manager 6.1, when I add the field and run the WPF client the field is always rendered as read-only - I'm expecting it to be an input field.
I've done the following
Added a new property to CATSRecord Object
Added the same property to the transaction CATSRecordAdd - linking to the CATSRecord object property
Added a new field on the CATSRecordAdd_Detail_Windows linked to the CATSRecordAdd transaction - I set the edit type as Decimal Number, there are no rules associated with it.
When I publish and run the application I can see the field on the screen, but the field is read only?
I checked and did the same process in Work Manager 5.3 (Agentry 6) in it's SDK and as expected the field rendered as input as expected.
I'm wondering why this does not render as an input field in Work Manager 6.1 - I further checked by simply selecting another existing field on the CATSRecord object (I selected the Counter property) and that rendered as input.
I'm running..
Work manager 6.1
Eclipse 4.2.2 Plugin 7.0.3.605
SMP3.0 SP03
I know SMP3.0 SP04 and SDK SP05 are due tomorrow so wondering if those patches will have any effect?
Thanks
Stu

Looks like my problem was related to the Crew Management module which I'd activated - that uses CrewCATSRecord not CATSRecord object. Modifying/adding new properties to that it now all good...

Work Manager 6.1 Sizing Guide Query

Hi,
Looking at the official Work Manager 6.1 sizing guide and comparing it to the Work Manager 6.0 guide and it seems there has been a large jump in the suggested hardware for SMP.
I understand the WM6.0 runs on SMP 2.3 and WM6.1 is on SMP 3.0, but I'm surprised that the difference seems so large.
E.g. For a medium landscape with 1000 syncs/hour:
Work Manager / SMP
SMP SAPS (suggested)
Work Manager 6.0
2,000
Work Manager 6.1
55,500
Could someone clarify why this would be?
Thanks,
Stephen

The Sizing Document has been updated for the SMP Server and appear to be much more reasonable.
The SAP ABAP & DB Server recommondations are still the same and don't seem right.
E.g
Large Data Volume & 2000 syncs/hr
SAP DB Server - 393,500 SAPS
SAP ABAP Server - 127,500 SAPS
From the Sizing benchmarks an IBM Server with 271,080 SAPS has 8 Processors / 120 Cores / 1TB of RAM
Cheers,
Stephen

Work Manager 6.1 on SMP 3.0 HEC

Hi Experts,
I want to deploy work manager 6.1 on HANA Enterprise Cloud-HEC. Is it possible,if so please provide document or procedure.
Thanks in Advance
Regards,
Sravanthi

SMP Cloud doesn't have Agentry Support currently.

Work Manager 6.1 and SMP 3.0 with Agentry new features

Hi,
I know that Work Manager 6.1 is expected to be released by the end of June but I can't find any information about the product.
Since I'm starting a new project initially thought for Work Manager 6.0 but running in SMP 3.0, I would like to know the list of new features of 6.1 version.
At the same time I would like to know if the use of SMP 3.0 brings to the Agentry applications improvements regarding error handling, logging and administration in general since that was a bit poor in the previous versions.
The only thing I found regarding 6.1 version is this PDF where new functionalities regarding localization of assets in a map are added. I hope there is more than that.
Thank you for your help.

I guess the following thread answers my questions (except regarding SMP 3.0 logging, administrating and error handling with Agentry): http://scn.sap.com/message/15086739
I copy&paste the basic things to know:
More news during/after Sapphire
New features:
Based on SMP 3.0 using websockets for communication
GIS (ESRI) integration via Open UI
Visual Enterprise 3D integration via Open UI
SAP JCO 3 Support
Crew Management
WRP Customer Service
UX Improvements

Work Manager 6.1.0.4 configuration

Hi all,
currently Im trying to create connection from a iphone (work manager app installed) to an SAP Backend. Everything is set up and running (agentry server). Everytime i want to reach the server i get the next error message:
(On my iPhone)
Requesting Public Key from Server
SSL Invalid Chain
Communications error (14)
Connection failed
Ending transmission
(On backend log)
error:2006F067:BIO routines:BIO_read:connect error, ..\Socket\openSSLsockets.cpp#893:OpenSSLstreamSocket::SSLStreamSocket::checkSSLerror
Please can someone help me with this?
Thank you!

The error you are seeing indicates that the certificate presented by the Agentry server to the client (iPhone) is not trusted or the name on the certificate does not match the server name entered on the Agentry Client.
If you generate your own certificate for the Agentry server you will need to install the root CA certificate used to sign it as a trusted authority on the iPhone. I usually just email the root certificate file to myself and open it from the mail app on the phone to install.
Secondly even if the root CA is trusted, the name you enter when connecting the first time must match the name on the certificate. For example if the certificate is generated for myserver.mydomain.com but when I enter the server infomration on the iPhone I only enter myserver as the name even though the netowrk will properly route the connection to the server using only the hostname I will still get an error since what I entered doesn't match what is on the certificate. I believe you will get a different error message but it is still a key thing to consider.
--Bill

Work Management

Similar Messages

Maybe you are looking for