Raising a QMSM event with change doc MELDUNG - possible?

[Hilsbos, Margaret A]

Jocelyn,

Thanks for the suggestion. I considered using status management but it looks like I would need the user to manually set a user status. So that would be an extra step for the user that we'd like to avoid if possible.

Also I need to get the previous value for responsible and it seems I need to get that from the change document. So it seemed logical to use the change doc to raise the event. However as Anna pointed out, the SAP event responsibleIsChanged is raised automatically by the program.  If I have to query for the old PARNR value then I can just use the program-raised event to trigger the workflow.

Thanks,

Margaret

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]On Behalf
Of Dart, Jocelyn
Sent: Monday, November 28, 2005 7:12 PM
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