StarOffice for work management

I just started to use StarOfficeDrawing7.0 to make a schedule. My effort failed and I abandoned the effort because I could not establish the drawing size, reading the book, using the help or surfing the commands atop the drawing screen.
So here is my idea for StarOffice to leapfrog Microsoft Project. Project Management software is based upon projects. There is more on people's to do list than project tasks.
Project Managers would like resources to only consider the project tasks, and they don't want to undermine the 'Critical Path Method' (CPM)architecture. CPM breaks down in the engineering/design phase of projects, where the resources have other things to do and manage besides projects.
The method to manage engineering/design resources is basically to list the things to do, priortize them, estimate the duration of each thing to do and calculate when it will be done. Combining 'Outlook', Database and a drawing tool (with an interface to Project Management tools is what is needed.
Furthermore I analyze there is up to a 7 to 1 savings in paper by formating schedules, project and non-project, with the ability to display more than one activity per line. It is the format used for hundreds of years of scheduling before CPM, otherwise known in the PM industry as Arrow Diagraming Method or 'activity on arrow'. More details can be seen on www.commitmentscheduling.com that has a pdf and 16page white paper.
I know it works. I was the architect of such an application, used to schedule 350 engineers for 3 years.

Hi Anish,
Check out the below link,
http://help.sap.com/saphelp_erp2005vp/helpdata/en/c6/4dc955eafc11d18a030000e829fbbd/frameset.htm
hope it helps.
Assign points if found useful,
Regards,
Mani.

Similar Messages

Problem in adding Custom Provider for Work Management Service

Hello,
I'm facing an issue in adding custom provider for work management service. As you are aware, Work management service is a Provider model and we
can integrate with other systems by adding custom providers. So with that confidence, i have started writing a connector as mentioned below.
Step - 1: Added new provider xml in the below path
"C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\CONFIG\WorkManagementService\Providers"
Provider Name: provider.bizagitasklist
Provider XML Content:
<Provider ProviderKey="DAA52AF3-A147-4086-8C0C-82D2F83A089D" OverrideProviderKey="" Assembly="adidas.TaskProvider, Version=1.0.0.0, Culture=neutral, PublicKeyToken=5d6f3e6be60a351b" > </Provider>
Step -2: Added a class which inherits "IWmaTaskProvider" and implemented the override methods.
public class BizAgiTaskListProvider : IWmaTaskProvider
public string LocalizedProviderName
get { return "BizAgiTaskListProvider"; }
public string ProviderName
get { return "BizAgiTaskListProvider"; }
public Microsoft.Office.Server.WorkManagement.CalloutInfo GetCalloutInfo(IWmaTaskContext context, string taskExternalKey, string locationExternalKey)
return null;
public DashboardExtensionInfo GetDashboardExtensionInfo(IWmaBasicProviderContext context)
return new DashboardExtensionInfo { ClassName = "SP.UI.SharePointExtension" };
public BulkEditResult HandleBulkEdits(IWmaTaskContext context, BulkEdit updates)
return null;
public TaskEditResult HandleTaskEdit(IWmaTaskContext context, BaseAggregatorToProviderTaskUpdate taskUpdate)
return null;
public void RefreshSingleTask(IWmaTaskRefreshContext context, string externalKey)
public void RefreshTasks(IWmaTaskRefreshContext context)
//context.WriteProviderCustomData(
Step – 3: Written a class to fetch the tasks from BizAgi System which has method to provide the task data.
But I’m not able to feed those tasks in the class written in Step – 2 as I’m able to find any method which will take Tasks as Input and I’m not
sure about the format of tasks.
I’m able to debug the provider, and the breakpoint hitting in only one method and two properties.
(LocalizedProviderName, ProviderName, GetDashboardExtensionInfo).
Can you please help me to proceed further in implementing the above solution?
Best Regards
Mahesh

Hi Mahesh,
Although the implementation of work management service application is based on the provider model, I reckon the current SP 2013 RTM does not support custom providers. Only SharePoint task lists, Project server and MS Exchange are supported for now.
Regards,
Yatin

Work Manager 6.0 for SMP 2.3 - standalone server - Startup Exceptions

Hello Experts.
I am installing a standalone Agentry Server for Work Manager 6.0 on the server where we have installed SMP 2.3.
It has been installed successfully and does start up, however I get some annoying error messages during start up.
It seems that the server is running - I can succesfully synchronize to an ATE client.
Due to the results from this thread, I have changed all ports in the Agentry.ini file to separate ports numbered 7521, 7522, 7523 and 7524.
Port issues - SMP and Agentry
Errors from the startup.log:
13:26:00 05/05/2014: HTTP-XML Back End Back End: Started
13:26:00 05/05/2014: Server: Starting threads.
13:26:00 05/05/2014: 1 initial threads. Threads will auto-scale.
13:26:00 05/05/2014: Event: 20, 4, Server v6.1.0.3
13:26:00 05/05/2014: Starting front ends
13:26:00 05/05/2014: ANGEL Front End: Starting threads.
13:26:00 05/05/2014: Exception: 13:26:00 05/05/2014 : 2 (Socket Error), UNKNOWN (UNKNOWN, ), ..\Socket\win32\sockets.cpp#1514:ListeningStreamSocket::OSListeningSocket::listenOn
13:26:00 05/05/2014: 3 initial threads. Threads will auto-scale.
13:26:00 05/05/2014: ANGEL Front End: opening listen socket on port 7523
13:26:00 05/05/2014: Exception: 13:26:00 05/05/2014 : 2 (Socket Error), UNKNOWN (UNKNOWN, ), ..\Socket\win32\sockets.cpp#1514:ListeningStreamSocket::OSListeningSocket::listenOn
13:26:00 05/05/2014: Event: 17, 10, 0.0.0.0:7523 open
13:26:00 05/05/2014: Event: 17, 10, ANGEL Front End v6.1.0.3
13:26:00 05/05/2014: Exception: 13:26:00 05/05/2014 : 2 (Socket Error), UNKNOWN (UNKNOWN, ), ..\Socket\win32\sockets.cpp#1514:ListeningStreamSocket::OSListeningSocket::listenOn
13:26:00 05/05/2014: Event: 0, 0, Old log files moved into Logs-Rolled\2014-05-05-132546
13:26:00 05/05/2014: Event: 0, 23, 4
13:26:00 05/05/2014: Exception: 13:26:00 05/05/2014 : 2 (Socket Error), UNKNOWN (UNKNOWN, ), ..\Socket\win32\sockets.cpp#1514:ListeningStreamSocket::OSListeningSocket::listenOn
13:26:01 05/05/2014: Event: 0, 2, Server startup is complete.
13:26:01 05/05/2014: Agentry Application startup complete
Can anybody help with the meaning and implications of these errors ?
Thank you.
Søren Hansen.

Damn... I missed one port
You are correct. The default port (8282) of Agentry is used multiple places in the Agentry.ini file, and collides with SMP.
Thanks Steve.
For others:
Please make sure the following ports of the Agentry.ini file are unique across all applications on the server. In this case I have chosen to call all my ports on this instance 752X.
Now the server starts without errors.
[ANGEL Front End Ports]
1=7523
[TCP Front End]
listenOn=7521
[Java-1]
nonStandardJavaOptions=-Xdebug -Xrunjdwp:transport=dt_socket,address=7524,server=y,suspend=n
[HTTPXML-2]
baseURL=http://localhost:7522
listenOn=7525
Søren Hansen.

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 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

Accessing attachments stored in Open text (ECC) with Work manager 6.0

Hello Experts,
We are using Open text in one of our ECC systems to store documents, files, pdfs and other attachments for the Work Orders and Notifications.
We want to configure the Work Manager 6.0 application hosted on SMP2.3, in order to fetch all the Work orders in the mobile device.
Now the question is - Can we access the attachments on the mobile device, from the out of the box Work Manager configuration.
Or, is there a need to install any plug-ins in the ECC/Agentry side to enable the same.
Thanks,
Abhishek

Hi Abhishek,
This isn't out of the box functionality for Work Manager so you'll need to enhance the existing functionality.
To access OpenText Attachments (via ArchiveLink) in WorkManager try looking at the following->
1. Get Attachments
BAPI Wrapper - /SMERP/CORE_DOBDSDOCUMENT_GET
MDO Class - /SMERP/CL_CORE_KWDOCUMENT_DO (Method - GET)
You'll see the above GET method calls (If you GOS_ACTIVE flag is true) - GOS_DOCUMENT_GET_INFO
This is responsilbe for getting the attachment metadata returned to the Work Manager Client ->
ET_COMPONENTS
ET_SIGNATURE
ET_CONNECTIONS
To get the attachment metadata stored in OpenText via ArchiveLink look at the below Function Modules -
ARCHIV_GET_CONNECTIONS
ARCHIVOBJECT_STATUS
You could enchance the GOS_DOCUMENT_GET_INFO method with a Post-Exit method or Implement the BADI /SMERP/MDO_CORE_DOCUMENTS - END_BDS_FETCH
2. Create Attachments
BAPI Wrapper -/SMERP/CORE_DOBDSDOCUMENT_CRT
MDO Class - /SMERP/CL_CORE_KWDOCUMENT_DO (Method - CREATE)
This calls the method BDS_DOCUMENT_CREATE to create the file and store it against the Work Order / Notification.
You could look at following Function Modules ->
ARCHIVOBJECT_CREATE_TABLE (Create the file on the OpenText server)
ARCHIV_CONNECTION_INSERT (Link the newly created file with the Work Order / Notification)
The BADI doesn't provide a corresponding Create method so you could enhance the MDO class /SMERP/CL_CORE_KWDOCUMENT_DO with new method that calls the ArchiveLink Logic instead of the BDS_DOCUMENT_CREATE method. The new method can be configured via the Syclo Config Panel to be called instead of the standard CREATE method.
Also check out the document - Document Upload & Download handling in SAP Work Manager 6.0
Section 7 & 8 covers the BAPI Wrappers/Class Handlers & Ehancement Spots for Document handling
Hope that helps.
Cheers,
Stephen

Upgrading work manager 5.3 to 6.1 with out SMP 3.0

Hello Experts,
As per the blogs and posts, work manager 6.0 is designed for SMP 2.3 and work manager 6.1 for SMP 3.0.Can we use work manager 6.1(with its additional features)without SMP 3.0 similar to work manager 5.3.Can we have standalone work manager 6.1 server or we need to install complete SMP 3.0 runtime .
Please suggest can we upgrade work manager 5.3 to 6.1 without SMP 3.0 to have standalone Agentry server for work manager 6.1(Like standalone server for work manager 5.3)
Thanks in advance
Thanks & Regards,
Sravanthi Polu

Hi Bill,
Thanks for your reply.What about the customization's done in Work Manager 5.3, will they have impact when we upgrade from 5.3 to 6.1 on SMP 3.0.What is the better approach to retain the custom logic if we go for upgrade(SMP 3.0).As per my knowledge if we go for 6.1 on SMP 3.0, then custom logic need to be implemented again, so considering customization's as higher priority, can we migrate existing Work Manager 5.3(With custom logic(Editor,Java,ECC Changes)) to SMP 3.0.If we migrate custom logic would be retained,but can we make use of the new features in SMP 3.0 like open ui,client branding .... etc.
Please help in this regard.
Thanks in advance.
Regards,
Sravanthi

Work Manager API in Sun Java Application Server 8.1

I am trying to build a parallel application using Work Manager api (javax.resource.spi.work.WorkManager;)
I studied the Websphere implementation of WorkManager there you need to make JNDI lookup for work manager and then use it to submit the work.
My question is if i make class which will implement the javax.resource.spi.work.WorkManager; interface and use that class to submit the work and execute it in parallel then will that class will handle the resource management and all j2ee services
Do we have separate implementation of work manager API for Sun Java Application Server 8.1 (any jar like asynch.jar in IBM websphere) so that we will just create a work manager using admin console and make JNDI lookup and use it
Please guide me

Before I start, disclaimer -- I have no knowledge of Hibernate and the following comments are based on the stack trace you have included.
I think your permissions might be set all right but you might have an error in the hibernate query. It looks like hibernate uses antlr to parse the queries. While parsing the query, antlr is encountering an exceptional condition and is trying to exit the VM (by calling System.exit()). Obviously, the hibernate code does not have that permission and therefore the exception is logged.
My guess is if you fix the query such that hibernate/antlr can parse it, you will not run into this error.
Hope this helps,

Upgrading SAP Work manager 5.3 to 6.1 on SMP 3.0

Hi Experts,
We have SMP 3.0 server,work manager 5.3.Now want to upgrade from 5.3 to 6.1 and deploy standard work manager 6.1 (without crew management,meter management,customer service,linear asset management components)on to SMP 3.0
Agentry Editor and SMP 3.0 server are in different systems
Please suggest prerequisite add-ons needed,development and customization guides(for work manager 6.1 on SMP 3.0)
Manju Venkatesha, Please suggest in this scenario.
Thanks
Siva chandu
Tags edited by: Michael Appleby

Deploying WM 6.1 on SMP 3.0 can be found in
http://scn.sap.com/community/mobile/blog/2014/08/30/quick-start-guide-sap-work-manager-6x-with-smp-agentry
Thanks
Manju

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

Book For SAP SYCLO Agentry Work Manager 6.0

Hi Expert's,
Can any one suggest me the book for SAP SYCLO Agentry Work Manager 6.0 , Which covers End-To-End Implementation methodology?
Answer appreciates.
Thanks
Rag
Tags edited by: Michael Appleby

Moved to SAP for Mobile. Application related, not SMP.
Regards, Mike (Moderator)
SAP Customer Experience Group - CEG

How to use a work manager dedicated for an URI

Hello,
I have a servlet able to manage different use cases, based on differents URI (the servlet is mapped on /*, and depending of the URI and the configuration, I do different work)
I would like to set a workmanager on each of my use cases.
Is it possible to set a workmanager on a use case without any update of the descriptor files ? (without multi mapping the servlet because my use cases are pluggables)
I've seen it is possible to acces a workmanager programaticaly (commonJ work managers) but it seems to be mandatory to reference the commonJ work manager inside the web.xml file to allow loca JNDI lookup on this work manager. Thus If I add a work manager, I have to update the web.xml. There is another possibility without updating any deployment descriptors ?
Thank you very much for your answers,
Best Regards,
C.

James,
thank you for your update.
1) Concerning the first solution (CommonJ WM), it sounds good for my needs but I still have to update the web.xml to add the resource-ref to access the WorkManager by JNDI:
<resource-ref>
    <res-ref-name>wm/TestWorkManager</res-ref-name>
    <res-type>commonj.work.WorkManager</res-type>
    <res-auth>Container</res-auth>
    <res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>So I have to update my ear, it is not exactly what I want :(
2) Concerning the deployment plans, it is also a good idea, I can multiinstance a servlet to use different mapping and then apply different workmanager for different uris,
This is working. I update the web.xml using a deployment plan.
The only negative point is I can't only apply the deployment plan but I have to redeploy the entire application (wich is not recommended for production because it occurs a out of service period)
Do you know any solutions for this two points ?
Thank you a lot
Best regards,
C.

Tools for SAP development work management?

Hi fellow SAP developers!
As you know, in a big software company the management of development work can be a challenge. Everyone should be able to see quickly who is doing what, who is available for new work, how did some old requests get solved and where is their documentation. We are talking about more than just some simple ticket management system here. It would be a central repository and work management tool for years to come.
I am interested to hear some suggestions for good tools that can be used for development work management in SAP world.
- It should be a tool where development requests can be input, reviewed, approved, documented and stored.
- It should support storing attachments
- It should support a project structure, under which the development items are created.
- It should be searchable and have different views to the development requests (for example by project, request raiser, developer, status etc.)
- It should have some kind of approval system or workflow.
- It should also support email notifications when the status or person assignment changes.
- It should run on large corporate network (accessible in intranet, perhaps via browser).
- A nice bonus would be a mobile client access for urgent cases
I'm keen to hear any proposals, even if not all the points in the wishlist are fullfilled
I'm interested to hear any comments on your exeperiences on various work management tools. What worked and what not?

Well, a SAP based product would be efficient as it is integrated and there would be no need for additional licenses etc.
I have to investigate the Solution manager offerings more, if that indeed could handle this task. Have you got any further information or experience?
Rally sounds interesting as well! Are there any other tools like that, proven good in SAP development?
For simply using Abap workbench, I'm afraid that is not good enough for what I'm after. How would you manage for example work queues, project based issue views and extensive solution documentation with it? And everything would have to be searchable and visible for also for non-technical managers who do not log in to SAP.

Using work manager for third party connections

Folks we are trying implement work manager to
Allthough WL is self tuning, and you could "increase the internal socket pool", you have to fully understand the implications of this.
-It increases the # of threads, which ultimately degrades performance, due to the amount of context switching which would have to occur (this is at the application layer)... in general
-It will require additional memory, of which, we'd need to account for this, otherwise, it can run the WL instance out of memory, if we're in a fault condition
Let me explain this "fault" condition a little further...
There's a BIG difference between a 3rd party being down, and a 3rd party being able to respond to our request, but unable to process it in a timely fashion (i.e. they're overloaded, or the tcp connection is happening properly, but the application response from the 3rd party isn't properly responding/working in a timely fashion). We've seen this condition on a # of occasions and need to be able to have a max limit or governor on each 3rd party... of which, my understanding of WL work managers allows for this (I do have to note, I am not experienced with these, and my knowledge is only with what I've had time to read on). Ultimately, I'm trying to prevent the condition I've seen in a # of serious "slow downs" or hang-ups within the application... we should NOT be able to have 3rd party calls hamper the performance or availability of our application

Note that you can reduce the context switching by 'pinning' certain CPUs to handle, for example, the network interrupts.
You can use (on Linux): cat /proc/interrupts (shows information related to hard interrupts).
From http://middlewaremagic.com/weblogic/?p=8133
"In a multi-processor environment, interrupts are handled by each processor. Two principles have proven to be most efficient when it comes to interrupt handling:
Bind processes that cause a significant amount of interrupts to a CPU. CPU affinity enables the system administrator to bind interrupts to a group or a single physical processor (of course, this does not apply on a single CPU system). To change the affinity of any given IRQ, go into /proc/irq/<number of respective irq>/ and change the CPU mask stored in the file smp_affinity. To set the affinity of IRQ 19 (which in the above example is the network interface card) to the first CPU, we can use echo 2 > /proc/irq/19/smp_affinity."
To configure a work manager properly, you have to throttle the maximum threads and the capacity. The maximum number of threads are the number of threads
that are allowed to run simultaneously. Usually, you set this equal to some resource (such as the number of connections in a data source). This to prevent
contention for that resource (otherwise the thread would be waiting for the resource and thus consuming CPU cycles by polling if can go or not). When the maximum
is reached no other threads are spawned to run. The request that comes in is put into a piece of work and stays that way until an execute thread comes available
to process that work. The number of work instances you allow in your heap can be set by the capacity constraint (which thus throttles the memory consumption).
When the capacity is reached, new requests are rejected.

Working Space for Color Management...

Hello,
I'm working on a project with a series of still, all of which contain embedded sRGB color profiles (as these images were originally used for a web-based job). This video project will eventually go onto a SD DVD to be displayed on a SD NTSC television. When choosing my working space (for color management), should I use SDTV NTSC (or should I use sRGB and then specify SDTV NTSC in my output setting upon rendering? I'm leaning towards SDTV NTSC as my working space, but since I'm coming at this from a print background in color management, I'm wondering if someone could lend some advice?
Also, what should I select for these options (under Color Settings in Project Settings)...ie. should I or shouldn't I have them checked...
- Linearize Working Space
- Blend Colors Using 1.0 Gamma
Thanks!
Kristin.

> It didn't really touch on "Blend Colors Using 1.0 Gamma" though would I want this checked?
Generally, yes. It helps avoid problems that can occur with inter-layer blending.
> And pretty sure, for what I'm doing, I wouldn't want "Linearize Working Space" checked.
Also correct, unless you intend to work in a 16- or 32-bpc mode.
More information and additional helpful links are on the Help page for these topics:
http://help.adobe.com/en_US/AfterEffects/9.0/WS2A3CEB0E-F1A1-4035-9C62-CFF4A0527B11a.html

StarOffice for work management

Similar Messages

Maybe you are looking for