Workflow status 'Ready' but does not move on

Gaurav Naik khalnayak40000 at yahoo.com
Wed Nov 30 01:12:16 EST 2005


Hi Klaus,
   
  Please check the transaction SM58 for batch user WF-BATCH if it is a background task.
   
  It will show you the relevant message.
   
  Cheers,
  Gaurav

sap-wug-request at mit.edu wrote:
  Send SAP-WUG mailing list submissions to
sap-wug at mit.edu

To subscribe or unsubscribe via the World Wide Web, visit
http://mailman.mit.edu/mailman/listinfo/sap-wug
or, via email, send a message with subject or body 'help' to
sap-wug-request at mit.edu

You can reach the person managing the list at
sap-wug-owner at mit.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of SAP-WUG digest..."


Today's Topics:

1. RE: Raising a QMSM event with change doc MELDUNG - possible?
(Michael Pokraka)
2. RE: Workflow status 'Ready' but does not move on
(Baunach, Natasha R)
3. RE: Workflow status 'Ready' but does not move on
(Klaus-Dieter Spatz)
4. RE: Raising a QMSM event with change doc MELDUNG - possible?
(Kisloff, Philip B)
5. Can't single step through RH_ORG_INFO_AND_TASKS (Rick Sample)
6. RE: Workflow status 'Ready' but does not move on
(Baunach, Natasha R)


----------------------------------------------------------------------

Date: Tue, 29 Nov 2005 08:22:37 -0800 (PST)
From: Michael Pokraka 
To: "SAP Workflow Users' Group" 
Subject: RE: Raising a QMSM event with change doc MELDUNG - possible?
Message-ID: <20051129162237.30961.qmail at web30202.mail.mud.yahoo.com>
In-Reply-To: <87548400CF397141B3EA2B66CC2F7B9E124D6706 at CORPMAIL1.corp.dayzim.com>
Content-Type: text/plain; charset=iso-8859-1
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: list
Reply-To: SAP Workflow Users' Group 
Message: 1

Hi Margaret, 
Always happy to help someone who has clearly spent some time and effort to try
and figure it out: 

Hit F1 on the fields in SWEC and it gives you template FM's to copy to your own
:-)

I'm not sure how to do multiples of the same events without messing about with
it myself, so I'll stick to raising one event with a multiline container
element of your own type contianing the change(s) - key, old and new. So add a
custom FM to populate container and inside your copy of
SWE_CD_TEMPLATE_CONTAINER_FB_2, you'd do something like: 

Data: l_cdpos like cdpos,
l_changes type zQmsmParnrChgs " Your custom struct
t_changes type standard table of zQmsmParnrChgs.

* Add all changes to table
loop at changedocument_position into l_cdpos
where tabname = 'QMSM'
and fname = 'PARNR'.
...assign l_cdpos-key/old/new to l_changes-parnr/old/new
...and append to t_changes
endloop.

if sy-subrc = 0.
* Add table to event container
call method event_container->set
exporting
name = 'ChangeList' " Your event parameter name
value = t_changes.
endif.

Should work... unchecked, untested, standard disclaimers apply. 
Cheers
Mike



--- "Hilsbos, Margaret A" wrote:

> Mike,
> 
> Thanks...I'll give this a try.
> 
> I'm pretty weak at ABAP so if there is an example of what this might look
> like... :-) 
> (You could save me some time; I'll struggle through it though if need be)
> 
> It seems like the best approach if I can't fill the event container using the
> program-raised event as Anna suggested.
> 
> Margaret
> 
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]On Behalf
> Of Michael Pokraka
> Sent: Monday, November 28, 2005 5:09 PM
> To: SAP Workflow Users' Group
> Subject: Re: Raising a QMSM event with change doc MELDUNG - possible?
> 
> 
> Hi Margaret, 
> OK you laid down the challenge, so here goes: 
> 
> You're mostly on the right track, but keep the event at the same level as
> your
> change doc, i.e. stick to the notification. Create an event
> ZRESPONSIBLEPERSONCHANGED with event parameter(s). 
> 
> In SWEC, specify your event using a FM - the changedocs are provided as
> parameters for your entertainment. 
> The other FM in there is one for populating the event container, which is
> where
> you can put the Task number and old/new values.
> 
> A design choice that depends on your intended usage is whether to have
> multiple
> events with one per task, or one event with all changed tasks as a multiline
> parameter. 
> 
> Cheers
> Mike
> 
> --- "Hilsbos, Margaret A" wrote:
> 
> > Hello WUGers,
> > 
> > I have a perplexing little problem that I'm betting someone here knows just
> > the answer to.
> > 
> > I want to trigger a WF based on a change in the field QMSM-PARNR, which
> means
> > a change to the "person responsible" for a task on a service notification
> (or
> > q-note, etc). But the only change document I found is MELDUNG, which is
> based
> > on the key for the notification, not the task. Since there can be many
> tasks
> > on a notification, it is possible that more than one task will have this
> > field changed in a single transaction. We need to trigger a workflow for
> each
> > task that is changed, or at least loop through a set of work items for each
> > task that was changed. We also need to be able to identify the old and new
> > values in QMSM-PARNR.
> > 
> > QMSM-PARNR old and new values are written to CDPOS but I am unclear how to
> > handle the event trigger. SWEC wants an object like BUS2080 and CDHDR only
> > has the notification number as the key. I was wondering if I could use a
> > function module in SWED to translate the object key, using CDPOS -TABKEY 
> to
> > get the key for QMSM....but I'm guessing I can't trigger separate events
> for
> > each TABKEY value on a single change document.
> > 
> > Alternatively I think I could trigger the event based on BUS2080 and loop
> > through values in the workflow, using a multiline container element...but
> in
> > that case do the old and new values alternate in the container element? It
> > seems like it will be a pain to sort them out to the task numbers in the
> > loop. 
> > 
> > If I sound lost then I probably am... anyone want to help me out of the
> > wilderness? Can you give me a suggestion as to the best way to handle this
> > situation? 
> > 
> > Thanks!
> > 
> > Margaret Hilsbos
> > Day & Zimmermann
> > 
> > 
> > _______________________________________________
> > SAP-WUG mailing list
> > SAP-WUG at mit.edu
> > http://mailman.mit.edu/mailman/listinfo/sap-wug
> > 
> 
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
> 
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
> 

------------------------------

Date: Tue, 29 Nov 2005 08:23:31 -0800
From: "Baunach, Natasha R" 
To: "SAP Workflow Users' Group" 
Subject: RE: Workflow status 'Ready' but does not move on
Message-ID: <31F5998A44B92447BD334F8FBBA0B01F0AABF0BF at orsmsx401.amr.corp.intel.com>
Content-Type: text/plain;
charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: list
Reply-To: SAP Workflow Users' Group 
Message: 2

Klaus,

If it is a dialog step, did you remember to set it as General task or
assign specific agents as allowed agents for the task?

Natasha

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Klaus-Dieter Spatz
Sent: Tuesday, November 29, 2005 8:13 AM
To: 'SAP Workflow Users' Group'
Subject: Workflow status 'Ready' but does not move on

Hi All,

I do have a workflow method, which sits in the log with the status
'Ready'
but does not move on to the next step. 

Please see the attachment, perhaps someone has seen this before. 

Thanks Klaus

------------------------------

Date: Tue, 29 Nov 2005 08:34:11 -0800
From: "Klaus-Dieter Spatz" 
To: "'SAP Workflow Users' Group'" 
Subject: RE: Workflow status 'Ready' but does not move on
Message-ID: <016c01c5f502$bb3a7f80$283d1eac at DELLKDSSC>
In-Reply-To: <31F5998A44B92447BD334F8FBBA0B01F0AABF0BF at orsmsx401.amr.corp.intel.com>
Content-Type: text/plain;
charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Precedence: list
Reply-To: SAP Workflow Users' Group 
Message: 3

Natasha,

It is not a dialog step. It is supposed to process an update and just go to
the next step. 

Klaus

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of
Baunach, Natasha R
Sent: Tuesday, November 29, 2005 8:24 AM
To: SAP Workflow Users' Group
Subject: RE: Workflow status 'Ready' but does not move on

Klaus,

If it is a dialog step, did you remember to set it as General task or
assign specific agents as allowed agents for the task?

Natasha

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Klaus-Dieter Spatz
Sent: Tuesday, November 29, 2005 8:13 AM
To: 'SAP Workflow Users' Group'
Subject: Workflow status 'Ready' but does not move on

Hi All,

I do have a workflow method, which sits in the log with the status
'Ready'
but does not move on to the next step. 

Please see the attachment, perhaps someone has seen this before. 

Thanks Klaus

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug



------------------------------

Date: Tue, 29 Nov 2005 16:41:45 -0000
From: "Kisloff, Philip B" 

To: "'SAP Workflow Users' Group'" 
Subject: RE: Raising a QMSM event with change doc MELDUNG - possible?
Message-ID: <77B8D39FB855D511B6FE0002A55C0CE6051412FD at ukcfphmsx01.ukcf.astrazeneca.net>
Content-Type: text/plain;
charset="iso-8859-1"
MIME-Version: 1.0
Precedence: list
Reply-To: SAP Workflow Users' Group 
Message: 4

Hi Margaret,

Sorry, IHPA does record the partners for the task level. That was the point.
I don't see a need to create any additional events or ABAP code, but perhaps
I don't understand.

Regards

Phil


OBJECTCLAS MELDUNG 
OBJECTID 000600003730 
CHANGENR 718676 
TABNAME QMSM 
TABKEY 2000006000037300001 
FNAME PARNR 
CHNGIND U 

TEXT CASE 1 
UNIT OLD 
UNIT NEW 
CUKY OLD 
CUKY NEW 
VALUE NEW 50001984 
VALUE OLD 50001988 

-----Original Message-----
From: Hilsbos, Margaret A [mailto:Margaret.Hilsbos at dayzim.com]
Sent: 29 November 2005 15:22
To: SAP Workflow Users' Group
Subject: RE: Raising a QMSM event with change doc MELDUNG - possible?


Phil,

Thanks for your suggestion. However I've found that the change doc only
records QMSM-PARNR when I change the responsible on the task. I believe IHPA
only records the partners for the notification header level.

I was able to set the restriction in SWEC on QMSM-PARNR and raised my custom
event ZBUS2080.responsibleIsChanged2.

The issue at this point is handling the old and new PARNR values and
handling multiple changes per transaction. Mike P made a suggestion about
that, which I'll try as soon as I figure out how to code it.

Thanks,

Margaret

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]On Behalf
Of Kisloff, Philip B
Sent: Tuesday, November 29, 2005 8:27 AM
To: 'SAP Workflow Users' Group'
Subject: RE: Raising a QMSM event with change doc MELDUNG - possible?


Hi Margaret,

I have only raised a responsible is changed with Meldung for notifications,
and you are right, there is a problem with setting an event with QMSM in
SWEC(warning W8-706).

But this is not really a problem, because I still use MELDUNG and business
object BUS7051, as the changes to "partners" such as responsible person are
recorded in table IHPA, and it is IHPA-PARNR that you can set a field
restriction to in SWEC, not QMSM-PARNR. If you then go to the condition
editor you will then see IHPA_PARNR_OLD <> IHPA_PARNR_NEW. These IHPA
restrictions work for both notifications and tasks. 

After changing the task processor, I'm currently looking at an event log
entry with QMSM as the object type, but SWEC only has MELDUNG and BUS7051. I
imagine should also work for BUS2080.

Let me how you get on,

Best regards

Phil



-----Original Message-----
From: Hill, Anna [mailto:anna.hill at sap.com]
Sent: 29 November 2005 10:22
To: SAP Workflow Users' Group
Subject: RE: Raising a QMSM event with change doc MELDUNG - possible?


Margaret - I managed to check; the event is definitely raised as
standard on the system I'm currently on so it should also be for you.

Good luck!
Cheers
Anna
SAP UK

-----Original Message-----
From: Hill, Anna 
Sent: Tuesday, November 29, 2005 10:16 AM
To: 'SAP Workflow Users' Group'
Subject: RE: Raising a QMSM event with change doc MELDUNG - possible?
Hi Margaret

There is actually an event on the QMSM business object called
responsibleIsChanged so I expect there must be a way of raising this, if
it's not raised automatically by the application. I know that the
equivalent on BUS2080 is raised automatically but I can't test it for
QMSM as the system I'm on doesn't have th option available to enter
responsible users at task level. 

Try switching on the event trace (SWELS) for your user ID and change the
responsible field on a task to see if the event is raised as a first
option, if you haven't already done this. If this doesn't work then let
me know and we can have a re-think.

Cheers
Anna
SAP UK 


-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Dart, Jocelyn
Sent: Tuesday, November 29, 2005 12:12 AM
To: SAP Workflow Users' Group
Subject: RE: Raising a QMSM event with change doc MELDUNG - possible?

Have you checked out the option of using status management to notify the
workflow that person responsible has been changed? You would probably
need a user-defined status but both notifications and tasks are
transactions not master data and do a lot with status management so you
may have more luck there. 


Regards,
Jocelyn Dart
Senior Consultant
SAP Australia Pty Ltd.
Level 1/168 Walker St.
North Sydney 
NSW, 2060
Australia
T +61 412 390 267
M + 61 412 390 267
E jocelyn.dart at sap.com
http://www.sap.com


-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Hilsbos, Margaret A
Sent: Tuesday, 29 November 2005 7:20 AM
To: SAP-WUG (E-mail)
Subject: Raising a QMSM event with change doc MELDUNG - possible?

Hello WUGers,

I have a perplexing little problem that I'm betting someone here knows
just the answer to.

I want to trigger a WF based on a change in the field QMSM-PARNR, which
means a change to the "person responsible" for a task on a service
notification (or q-note, etc). But the only change document I found is
MELDUNG, which is based on the key for the notification, not the task.
Since there can be many tasks on a notification, it is possible that
more than one task will have this field changed in a single transaction.
We need to trigger a workflow for each task that is changed, or at least
loop through a set of work items for each task that was changed. We also
need to be able to identify the old and new values in QMSM-PARNR.

QMSM-PARNR old and new values are written to CDPOS but I am unclear how
to handle the event trigger. SWEC wants an object like BUS2080 and
CDHDR only has the notification number as the key. I was wondering if I
could use a function module in SWED to translate the object key, using
CDPOS -TABKEY to get the key for QMSM....but I'm guessing I can't
trigger separate events for each TABKEY value on a single change
document.

Alternatively I think I could trigger the event based on BUS2080 and
loop through values in the workflow, using a multiline container
element...but in that case do the old and new values alternate in the
container element? It seems like it will be a pain to sort them out to
the task numbers in the loop. 

If I sound lost then I probably am... anyone want to help me out of the
wilderness? Can you give me a suggestion as to the best way to handle
this situation? 

Thanks!

Margaret Hilsbos
Day & Zimmermann




_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug
------------------------------

Date: Tue, 29 Nov 2005 10:50:04 -0600
From: "Rick Sample" 
To: sap-wug at mit.edu
Subject: Can't single step through RH_ORG_INFO_AND_TASKS
Message-ID: <200511291650.jATGo78j004160 at ns3.graybar.com>
Content-Type: text/plain;
charset=us-ascii
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Precedence: list
Reply-To: SAP Workflow Users' Group 
Message: 5

I set my break points at the first executable statement in this FM. 
It never steps inside this FM. Never had this issue before. 
Anyone have a clues why?

In 4.6c srv pack 50

Thanks
Rick

------------------------------

Date: Tue, 29 Nov 2005 08:52:42 -0800
From: "Baunach, Natasha R" 
To: "SAP Workflow Users' Group" 
Subject: RE: Workflow status 'Ready' but does not move on
Message-ID: <31F5998A44B92447BD334F8FBBA0B01F0AABF152 at orsmsx401.amr.corp.intel.com>
Content-Type: text/plain;
charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: list
Reply-To: SAP Workflow Users' Group 
Message: 6

In your attachment, the step that is stuck in status Ready has icon for
agents. Background steps don't have that icon. Check on your task
definition to make sure that background checkbox is checked in the lower
left corner.

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Klaus-Dieter Spatz
Sent: Tuesday, November 29, 2005 8:34 AM
To: 'SAP Workflow Users' Group'
Subject: RE: Workflow status 'Ready' but does not move on

Natasha,

It is not a dialog step. It is supposed to process an update and just go
to
the next step. 

Klaus

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of
Baunach, Natasha R
Sent: Tuesday, November 29, 2005 8:24 AM
To: SAP Workflow Users' Group
Subject: RE: Workflow status 'Ready' but does not move on

Klaus,

If it is a dialog step, did you remember to set it as General task or
assign specific agents as allowed agents for the task?

Natasha

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Klaus-Dieter Spatz
Sent: Tuesday, November 29, 2005 8:13 AM
To: 'SAP Workflow Users' Group'
Subject: Workflow status 'Ready' but does not move on

Hi All,

I do have a workflow method, which sits in the log with the status
'Ready'
but does not move on to the next step. 

Please see the attachment, perhaps someone has seen this before. 

Thanks Klaus

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug



_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

------------------------------

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug


End of SAP-WUG Digest, Vol 12, Issue 143
****************************************
  


		
---------------------------------
 Yahoo! Music Unlimited - Access over 1 million songs. Try it free.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20051129/b9dd6e9c/attachment.htm


More information about the SAP-WUG mailing list