Raising a QMSM event with change doc MELDUNG - possible?

Kisloff, Philip B Philip.Kisloff at astrazeneca.com
Tue Nov 29 11:41:45 EST 2005


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


More information about the SAP-WUG mailing list